I have a couple questions about a use case. In general is it a security concern for your app that SQLite doesn't care about user permissions the way client/server DBs do? What is the best you can do? Just make sure the file perms are appropriate so that just your app can read/write it?
Also, The project I'm working on is a multi-client thing, but the vast majority of what happens would be a silo'd situation on Postgres. The webapp itself and site structure would be shared, but clients would create projects for data processing and analytics. Would it be reasonable to just create a new SQLite db file per project? In some ways that would make backups easier by project, but dumping all data for a client would kind of be a pain. Are there other gotchas about a structure like this?
Also, The project I'm working on is a multi-client thing, but the vast majority of what happens would be a silo'd situation on Postgres. The webapp itself and site structure would be shared, but clients would create projects for data processing and analytics. Would it be reasonable to just create a new SQLite db file per project? In some ways that would make backups easier by project, but dumping all data for a client would kind of be a pain. Are there other gotchas about a structure like this?