Hello, I was under the impress that we could never get an SQLITE_BUSY, not even on COMMIT if we use BEGIN EXCLUSIVE. But this seems to say that COMMITs on exclusive transactions can through SQLITE_BUSY?...
--- [EMAIL PROTECTED] wrote: > then start the transaction initially with BEGIN > EXCLUSIVE. This > will acquire the reserved lock immediately (instead > of waiting to > the first write occurs) and so you will either get > an SQLITE_BUSY > right away (when it is a simple matter to just rerun > the BEGIN EXCLUSIVE > statement until it works) or you can be assured of > never getting > another SQLITE_BUSY again until you try to COMMIT > (and there too, > you can simply rerun COMMIT repeatedly until it > works.) How is that? Since the process at that point has the exclusive access to the database file. Best regards, Kervin
