Integration with an app that's already using plain GRDB?

[fweez]

I work on a large application that currently makes heavy use of plain old GRDB to interface with a single database. This library looks great for us going forward, but I don't want to try to rewrite our existing code to use it all at once. Looking through the docs on sharing-grdb I don't see any obvious red flags to looking into incremental adoption, but are there any possible problems I should be aware of?

[mbrandonw]

Hi @fweez, the only thing that comes to mind is the fact that our tools prefer for your app to be using a single database connection (DatabaseQueue or DatabasePool), but that is probably a good recommendation for any SQLite-based application. And further, we require you put that database connection into the dependencies system using prepareDependencies. See the docs here.

Other than that, everything in this library is 100% additive to an existing GRDB application. You should be able to use @SharedReader(.fetchAll(…)) with a raw SQL query targeting your schema, or use @SharedReader(.fetch(…)) with a FetchKeyRequest conformance that uses GRDB's query builder.

Please do bring up any issues you come across though :)

[fweez]

Cool! Yeah, we're already passing around a DatabasePool throughout the app so this should be a pretty simple addition to new code.