2 ms·
You can run into problems if you have two threads handling two requests. Each of them might have a shared read-lock as they are getting data, and when they both
by remram 6y ago
You can run into problems if you have two threads handling two requests. Each of them might have a shared read-lock as they are getting data, and when they both try to update to a write-lock to do some update, one of them will be canceled (throw an exception: SQLITE_BUSY).
This seems to me like a Rails bug, it should be serializing transactions when running against SQLite.