4 ms·
Each user's account gets their own SQLite file. So now you need one database connection per user...
by Scarbutt 4y ago
Each user's account gets their own SQLite file.
So now you need one database connection per user...
- tptacek 4y agoAnd? It's SQLite; it's a file handle and some cache, not a connection pool.
- mwcampbell 4y agoDepending on how you define "account", that can be quite reasonable. In a B2B application, each business customer could get their own SQLite database, and the number of SQLite connections would likely be quite manageable, even though some customers have many users.
- robertlagrant 4y agoIf by connection you mean in-process database.
- freedomben 4y agoWithout knowing details about the app, it's hard to know if that would matter. If a small number of concurrent users would ever be using it, I would think it would be NBD.