@groue I opened a new discussion here:
https://github.com/groue/GRDB.swift/discussions/1821
Will describe the changes in a couple of parts to make it more manageable to write/read.
Fixed the build of GRDB on Linux and now trying to fix the failing tests. More than 400 tests are failing so it was difficult to see which tests were, but luckily I found:
🚀 I've just shipped #GRDB v7.6.1, that fixes a race condition introduced three days ago in v7.6.0: Please upgrade!
Version 7.6 makes it possible to access Task locals from async database accesses. This improves GRDB integration with toolings that rely of Task locals. For example, your tests can now use the #expect macro from within an async database access.
New blog post: Caveats Using Read-only SQLite Databases from the App Bundle
https://twocentstudios.com/2025/06/07/sql-databases-bundle/
A quick debugging story where I learned some new things about SQLite's journal mode while building an database export/import feature for Eki Live.
TLDR:
- Journal mode is embedded in the sqlite database file itself.
- The `backup` command changes the journal mode of the target database to match the source database.
- Check the journal mode of a database with `sqlite3 db.sqlite "PRAGMA journal_mode;"`.
- Change the journal mode of a database with `sqlite3 db.sqlite "PRAGMA journal_mode=DELETE;"`.
Just loving the SharingGRDB framework! The @pointfreeco guys really modernized swift persistence: https://github.com/pointfreeco/sharing-grdb
Getting a strange linker error with swift on Linux. I'm developing a cli app that uses another SPM package. That package uses GRDB and compiles. When trying to compile the cli app I get a linker error with sqlite3. In the screenshot below it looks like lsqlite3 has been included multiple times for linking? Anyone got an idea?