Gwendal Roué

🇫🇷 Ce compte est gelé. Pour me contacter au sujet de GRDB, ou autre, veuillez utiliser Mastodon ou GitHub. 🇺🇸 This account is frozen. To contact me about GRDB or any other topic, please use Mastodon or GitHub. @groue" target="_blank" rel="nofollow noopener">hachyderm.io/@groue github.com/groue

Départ de X enclenché : j'attends mon archive. C'était cool, Twitter, hein ? Les temps ont tellement changé. Bonjour 2025, bonjour l'Europe, bonjour l'avenir ! Pour continuer à me suivre, c'est sur @groue" target="_blank" rel="nofollow noopener">hachyderm.io/@groue. Time to leave X! See you soon on Mastodon 😙

@demensdeum The dump features are the base for the snapshot testing companion library swiftpackageindex.com/groue/GRDBSnap…. I wish more people would know about it!

@demensdeum You might be interested in the built-in dump features :) See for example swiftpackageindex.com/groue/grdb.swi…

This week we explore executing SQLite queries to fetch data and display it in SwiftUI. Along the way we showcase a technique for seeding data in development using GRDB migrations to instantly populate your UI with no additional work. 👉 pointfree.co/episodes/ep303…

Learn how to integrate SQLite into a SwiftUI view using GRDB. We’ll explore querying the database to display data in the UI, enforcing table relations to maintain app state, and testing everything in Xcode previews. 👉 pointfree.co/episodes/ep303…

Comparing code that interfaces with the SQLite C library and GRDB is like comparing night and day. Dozens of statements and lines of code that are easy to get wrong often turns into a single expression. Learn more: pointfree.co/episodes/ep302…

Interfacing with SQLite’s C library from Swift is possible but clunky. Thankfully, the community offers friendlier, more “Swift-like” options. Let’s explore the most popular one, GRDB, and show how it avoids boilerplate and catches issues at compile time. pointfree.co/episodes/ep302…

Like that crossover episode you didn’t know you needed - @pointfreeco featuring @groue’s incredible work on GRDB.swift ❤️

@krzyzanowskim Thank you :) Yes GRDB is not bad at database observation. The demo app contains a simple view model that observes a list of "players" with the ability to control how they are sorted. It is testable, and tested. #L39" target="_blank" rel="nofollow noopener">github.com/groue/GRDB.swi… All Swift 6-ready, with MainActor and all.

and before anyone ask: but what about observality, I have good news, it is often baked in the db engine. For this bubble, the GRDB is probably the right framework to go #executing-updates" target="_blank" rel="nofollow noopener">github.com/groue/GRDB.swi…

many does not realize that instead of fighting the fight with SwiftData year after year, a few SQL queries is way better approach. the effor programmers can make to avoid SQL amazes me.

🚀 GRDB 7 beta is out! forums.swift.org/t/grdb-7-beta/…

@jazzychad I should remove this paragraph from the documentation. I built several modularized apps without any issue. Maybe the Xcode bug no longer exist, or has moved (a few people are still discussing in the linked issue).

Lots of people recommending GRDB but this seems like a showstopper issue for building modern apps, which rely more and more on having extensions for system integration…?

@krzyzanowskim @pepicrft Not yet, but almost: @groue/112681119698160557" target="_blank" rel="nofollow noopener">hachyderm.io/@groue/1126811…

@pepicrft GRDB afaik

After switching from CoreData to GRDB, Avare's crash rate is significantly lower. 😍 0 reported crashes 😍 Anyone using Avare and experiencing a bug or crash? If so, please let me know 🙏🏻 #buildinpublic #iosdev

@everton_dev @esyx0 You might appreciate GRDB, actually. One can sure keep on ignoring relational databases, isolation levels, etc, when using it. But for the people who care, the library makes sure they can express themselves sharply.

@esyx0 I never tried GRDB, looks nice. But I meant more conceptually, all the theory behind how databases work. A lot of iOS devs seem to neglect learning databases, but it’s very important for us too.

As an iOS developer, have you explored databases? SQL vs. NoSQL, querying data, data normalization, and more?

@dexterleng In all cases, thanks for your feedback. If GRDB had throwing accessors, this would be less work for you, I can pretty well see that.

@dexterleng 👍 I see. Indeed you'll need Swift optional for all nullable columns. I don't know if this can help, but you could also derive a new database file from the original, where those columns are not nullable, and discard invalid rows?

praying this fixes the crashes.

@dexterleng This has been discussed in a repository issue (see link). Basically, wrong casts are assumed to be a programmer error, because the database schema is under the control of the programmer. github.com/groue/GRDB.swi…

GRDB using try! to decode and cast columns was something I didn't expect.

@arasan01_me Forked by @cmchen who has been using GRDB at Signal. Looks like when you go GRDB you're never going back 😉

BrowserCompanyがGRDB.swiftをForkしてる

@_williamkennedy @Jason80586 Don't hesitate opening a discussion about the kind of improvements you'd like to see!

@groue @Jason80586 Of course, it doesn't have to. It's perfect the way it is now.

One thing I like about native dev on Android compared to iOS is that SQLite is a first-class citizen in Android. You literally annotate methods with the SQL you want to execute. It's a very nice API. Compared to iOS, SQLite is not a first-class citizen, and there is work involved in setting up everything to use SQLite directly. Apple has Core Data or Swift Data which has a lot of magic. There are pros and cons to both, of course, but as a web developer, SQL is practically a first language.