|
|
|
|
|
|
by gwd
813 days ago
|
|
|
I'm relatively new to the DB field, and have only really used SQLite; but it seems obvious to me that if you're doing a transaction, particularly a complicated one, then you should expect your transaction to fail occasionally due to concurrent changes, and be executing your transaction in a loop. This should be true for any database. If you loop-retry all transactions which fail due to transitory effects, then you won't have a problem with "database locked" situations. Abysmally documented, but this is what I use for golang + sqlite: https://pkg.go.dev/gitlab.com/martyros/sqlutil@v0.0.0-202312... EDIT: Typo |
|
|