groue

7 ms·

1.
by groue 7mo ago
Gentium is a very beautiful font: https://software.sil.org/gentium/
2.
by groue 10mo ago
You are not your code.
3.
by groue 1y ago
Yes. GRDB encourages Codable because the user can profit from the code generated by the compiler, and this implies that database values are accessed by column name, on top of the Codable runtime, and those layers have a high cost. When nece
4.
by groue 1y ago
You're welcome :)
5.
by groue 1y ago
Thank you (GRDB author here). It is not mentioned in the README of the repository, but SQLiteData wraps GRDB to access the database and get notified of database changes (the meat and butter). GRDB is by itself a solid "toolkit for SQLi
6.
by groue 2y ago
Out of curiosity, I asked on the SQLite forum how the query optimizer fits in this schema: https://sqlite.org/forum/forumpost/93f9bfcec0
7.
by groue 4y ago
I do, for JSON columns. I store UTF8 strings in SQLite, so that it is easy to see JSON values with a plain `SELECT *`). And I load blobs, because I code in Swift and the standard JSON decoder eats raw UTF8 memory buffers, not strings. This
8.
by groue 4y ago
Yes. Now, many short writes look exactly as one very long write from the point of view of an enqueued write that is waiting for its turn :-) I don't quite remember how fair is SQLite scheduling, in practice.
9.
by groue 4y ago
What's cool with WAL mode is that SQLITE_BUSY won't happen for readers (except very rare scenarios: https://www.sqlite.org/wal.html#sometimes_queries_return_sql... ) One should only expect SQLITE_BUSY for writes (i
10.
by groue 4y ago
It is always safe, and by "safe" I mean "safe for data". You won't have to deal with data corruption. Precisely, see "How To Corrupt An SQLite Database File": https://www.sqlite.org/howtoco
11.
by groue 5y ago
The music is quite good! The covers of Freddie Freeloader and Flamenco Sketches are quite worth it, IMHO :-)
12.
by groue 5y ago
Library author here - SQLite concurrency needs a little care: don't miss the Concurrency Guide: https://github.com/groue/GRDB.swift/blob/master/Documentatio...
13.
GRDB 5.17 with async/await (SQLite toolkit for Swift)(old.reddit.com)
1 points by groue 5y ago|1 comments
14.
by groue 6y ago
You can try https://github.com/groue/GRDB.swift It's a thin wrapper around SQLite, with convenience APIs for record types, robust support for concurrency, and a focus on GUI apps.
15.
New release: GRDB 5.0.0 (Swift toolkit for SQLite databases)(forums.swift.org)
1 points by groue 6y ago|0 comments
16.
Swift Evolution – [Accepted] SE-0279: Multiple Trailing Closures(forums.swift.org)
1 points by groue 6y ago|0 comments
17.
Announcement: Version 5.0.0-beta of GRDB, the Swift toolkit for SQLite databases(forums.swift.org)
1 points by groue 6y ago|0 comments
18.
Announcing GRBD 4, a Swift Toolkit for SQLite Databases(forums.swift.org)
1 points by groue 7y ago|0 comments
19.
by groue 8y ago
I often promise myself to have a look at SQLite virtual file system API, for this very purpose, but could not yet find the guts :-)
20.
by groue 8y ago
We start to see ORMs like Diesel ( https://diesel.rs ) or GRDB ( http://github.com/groue/GRDB.swift ) that radically simplify their domain by removing traditional ORM features like implicit uniquing, lazy-loadi
21.
by groue 8y ago
Related article: "Automatic Undo/Redo Using SQLite" https://www.sqlite.org/undoredo.html
22.
by groue 9y ago
There are ORMs that address partial records, multi-threading troubles brought by lazy loading, uniquing, auto-updating records, and, importantly, put raw SQL on the same level as the query builder. I think of [Diesel]( http://dies
23.
by groue 9y ago
I agree. Sometimes, I explain that the feature request can be implemented, but not for free. I flag such issues with the "needs sponsoring" tag.
24.
SQLite: FMDB-compatible bindings to GRDB.swift(github.com)
1 points by groue 9y ago|0 comments
25.
by groue 9y ago
Unique to GRDB.swift, as far as I know, is the ability to perform database writes and then wait until snapshot isolation has been reached in another connection before releasing the writing lock. This allows to read from a known database s
26.
by groue 9y ago
I'd also like to thank the other for his attempt at raising the general awareness of transaction isolation. Even when you deal with simpler databases like SQLite, isolation is a serious topic. When serializing accesses hinders performa
27.
by groue 9y ago
> They sound similar to change data capture in SQLServer. Yes. There is a difference, though: SQLite is embedded, and there is zero latency between an application and its database. This means that change notifications can be emitted sync
28.
by groue 9y ago
I didn't know about windowing function. This page looks like a nice description: https://community.modeanalytics.com/sql/tutorial/sql-window-...
29.
Unexpected SQLite with Swift(medium.com)
1 points by groue 9y ago|5 comments
30.
by groue 10y ago
Sure, and French don't have a word for "entrepreneur" neither

More ›