🇫🇷 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.
https://t.co/umdB4SVJS3
https://t.co/fJdTHwVf9F
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 https://t.co/umdB4SVJS3.
Time to leave X! See you soon on Mastodon 😙
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.
👉 https://t.co/z4zfn8Lllj
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.
👉 https://t.co/z4zfn8Lllj
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: https://t.co/RZ3os17drP
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.
https://t.co/RZ3os16FCh
@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.
https://t.co/l69YsBLSOY
All Swift 6-ready, with MainActor and all.
@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).
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.
@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?
@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.
https://t.co/zCKgJXZwt6