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

2006-05-09 Thread Michael B. Hansen
:) /Michael -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 9. maj 2006 12:26 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Transactions and 'library routine called out of sequence' locks the database "Michael B. Hansen" <[

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

2006-05-09 Thread drh
"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 b

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

2006-05-08 Thread Michael B. Hansen
t the problem with SQLite continues. -Original Message- From: Dennis Cote [mailto:[EMAIL PROTECTED] Sent: 8. maj 2006 17:12 To: sqlite-users@sqlite.org Subject: Re: [sqlite] Transactions and 'library routine called out of sequence' locks the database Michael B. Hansen wrote: >

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

2006-05-08 Thread Dennis Cote
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

2006-05-08 Thread Michael B. Hansen
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 inte