rethinkdb_rebirth VS GRDB.swift

I know [RethinkDB][1] used to do this with their SQL-like ReQL language, but I looked around a bit and can't find much else about it - and I would have thought it would be more common.

If we think about modern frontends using SQL-based backends, essentially every time we render, its ultimately the result of a tree of SQL queries (queries depend on results of other queries) running in the backend. Our frontend app state is just a tree of materialized views of our database which depend on each other. We've got a bunch of state management libraries that deal with trees but they don't fit so well with relational/graph-like data.

I came across a Postgres proposal for [Incremental View Maintenance][2] which generates a diff against an existing query with the purpose of updating a materialized view. Oracle also has [`FAST REFRESH`](https://docs.oracle.com/database/121/DWHSG/refresh.htm#DWHSG8361) for materialized views.

I guess it's relatively easy to do until you start needing joins or traversing graphs/hierarchies - which is why its maybe avoided.

[1]: https://github.com/rethinkdb/rethinkdb_rebirth

I'm using GRDB , you can use existing pre-populated sqlite DB file. https://github.com/groue/GRDB.swift/wiki/Performance .

Not quite exactly sure what you mean but if its a .sqlite3 file then you can use it with this easy to use library https://github.com/groue/GRDB.swift

The 3rd party library I use GRDB SwiftyUserDefaults Kingfisher SwiftDate Popovers

The other thing is that it could be an overkill for your app if you just need to basically "store an array of 100 objects". Then you could probably consider other solutions like SQLite (with wrappers like GRDB) or plain JSON files.

https://github.com/groue/GRDB.swift#readme https://github.com/groue/GRDB.swift/tree/master/Documentation https://swiftpackageindex.com/groue/grdb.swift/documentation/grdb/

https://github.com/groue/GRDB.swift/blob/master/Documentation/AssociationsBasics.md might be interesting to look at for how it handles relationships between entities.

I recently used GRDB.

Check the performance comparison page. GRDB comes with a convenient and ready-made support for Swift Codable that performs quite well. When needed, it is possible to write less convenient but optimized record types that add very little overhead to SQLite, and perform really well.

Hey all. So I just got done developing an app that does visitation tracking. Basically the user creates an account with email, name, password etc.. the info is then saved to a SQLite database (using GRDB) with a table named "User" and then injected into the next view controller and so on... I plan on allowing the user to store their account in icloud in the future.