RE: [sqlite] Transactions and 'library routine called out of sequence' locks the database

Hi D. Richard, Your comments / suggestions made me think and widen my exception tracking - and it does indeed seem that it is caused by statement that fails with a NULL-pointer exception when sqlite3_prepare is called. Why this is I need to figure out - but I suspect that the Finisar.SQLite

Re: [sqlite] Transactions and 'library routine called out of sequence' locks the database

"Michael B. Hansen" <[EMAIL PROTECTED]> wrote: > > However, I keep getting 'library routine called out of sequence' at > random interval. > This is caused when you do things like try to use a database connection that has already been closed or try to use a prepared statement that has already

RE: [sqlite] Transactions and 'library routine called out of sequence' locks the database

Hi Dennis, Thank you for your reply :) I'm using SQLite in .NET through Finisar.SQLite wrapper. The locking mechanism is a static object which I use as a mutex by the .NET 'lock'-method. And finally - yes, I open and close the database in each transaction: Regarding the API that returns the

Re: [sqlite] Transactions and 'library routine called out of sequence' locks the database

Michael B. Hansen wrote: I use my own global locking-mechanism, so only one connection can be opened at one time. Michael, Is it possible that your "own" locking mechanism is failing? You haven't said how the locks are implemented, and getting mutual exclusion stuff right in roll your own

[sqlite] Transactions and 'library routine called out of sequence' locks the database

Hi, I have this problem - that keeps hunting me. I use SQLite 3.3.5 - with all queries, updates and inserts in transactions. I use my own global locking-mechanism, so only one connection can be opened at one time. However, I keep getting 'library routine called out of sequence' at random