12 ms·
It doesn't allow multiple concurrent writers easily - you have to handle the "SQLITE_BUSY" errors yourself and cope with any changes that might have happened in
by zimpenfish 9y ago
It doesn't allow multiple concurrent writers easily - you have to handle the "SQLITE_BUSY" errors yourself and cope with any changes that might have happened in the interim (although transactions can obviously help.)
https://www.sqlite.org/lockingv3.html https://www.sqlite.org/lockingv3.html