3 ms·
> what exactly do you do when you have failure Depends on the failure. What do you have in mind? > when more than one process need to acces the DB Easy, you
by warmwaffles 4y ago
> what exactly do you do when you have failure
Depends on the failure. What do you have in mind?
> when more than one process need to acces the DB
Easy, you use `journal_mode` set to `WAL` when you connect to the sqlite database.
> when you need RBAC
If you need RBAC, you aren't going to be using sqlite. In theory you could have your application handle the RBAC part since sqlite is embedded in your application.
Another solution is to leverage unix users and groups and set permissions appropriately for the database file and the application running.
- ju-st 4y ago>> when more than one process need to acces the DB > Easy, you use `journal_mode` set to `WAL` when you connect to the sqlite database. and set isolation level and check_same_thread and PRAGMA synchronous and then put all queries in retry loops because the DB is maybe locked https://sqlite.org/wal.html#sometimes_queries_return_sqlite_busy_in_wal_mode https://sqlite.org/wal.html#sometimes_queries_return_sqlite_... I wasted so much time trying to get multiple sqlite queries running at the same time
- warmwaffles 4y ago> I wasted so much time trying to get multiple sqlite queries running at the same time You were trying to write at the same time right?
- ju-st 4y agono, although the DB was not opened readonly mode. I tested with apachebench with many parallel requests on endpoints using only SELECTs