Stephen C. Gilardi wrote:
Of course I could implement this in the application code, but I'd
rather understand why sqlite isn't able to do this first. The sqlite
source is unfamiliar territory, but I'll have a poke around and try
to trace how the busy callback is used.
Based on following the
Paul Dixon wrote:
I'm having some problems with multi-threaded updates failing.
Multiple threads open their own sqlite connection with sqlite3_open()
and then call sqlite3_busy_timeout(handle, 3) to give a 30 second
timeout. These threads then perform some inserts on the same table, but
I get
I'm having some problems with multi-threaded updates failing.
Multiple threads open their own sqlite connection with sqlite3_open()
and then call sqlite3_busy_timeout(handle, 3) to give a 30 second
timeout. These threads then perform some inserts on the same table, but
I get "database is
3 matches
Mail list logo
