Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

[EMAIL PROTECTED] wrote: Dave Dyer <[EMAIL PROTECTED]> wrote: The real problem is that sqlite assumes it "owns" the temporary transaction file that it created, and can do anything it wants with it; for example read, rename, or delete it. I think this is a very reasonable assumption. Any othe

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

A. Pagaltzis wrote: * Roger Binns <[EMAIL PROTECTED]> [2006-06-05 00:05]: I don't know if anyone has tracked how well Spotlight (Mac) or Beagle (Linux) work with SQLite files. They cause no problems. The semantics of the filesystem API on *nix systems differ from those of Windows; in short, a

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

* Roger Binns <[EMAIL PROTECTED]> [2006-06-05 00:05]: I don't know if anyone has tracked how well Spotlight (Mac) or Beagle (Linux) work with SQLite files. They cause no problems. The semantics of the filesystem API on *nix systems differ from those of Windows; in short, a file and its name are

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

* Roger Binns <[EMAIL PROTECTED]> [2006-06-05 00:05]: > I don't know if anyone has tracked how well Spotlight (Mac) or > Beagle (Linux) work with SQLite files. They cause no problems. The semantics of the filesystem API on *nix systems differ from those of Windows; in short, a file and its name ar

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

"Roger Binns" <[EMAIL PROTECTED]> wrote: > > It may be worth considering a solution for all operating > systems. I don't know if anyone has tracked how well > Spotlight (Mac) or Beagle (Linux) work with SQLite files. > The problem seem to be two-fold: * Attempting to delete journal files th

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

> The obvious quick fix is to retry these file operations that must > succeed,... Can some windows programmers suggest patches to os_win.c to implement this. Subversion had the same issues for the same reasons. I'd suggest a similar solution and parameters: http://subversion.tigris.org/faq.h

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

Dave Dyer <[EMAIL PROTECTED]> wrote: > > The real problem is that sqlite assumes it "owns" the temporary > transaction file that it created, and can do anything it wants with it; > for example read, rename, or delete it. I think this is a very reasonable assumption. > Any other process which >

RE: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

I encountered this problem and agree with most of the diagnosis. The real problem is that sqlite assumes it "owns" the temporary transaction file that it created, and can do anything it wants with it; for example read, rename, or delete it. Any other process which gets it's hooks into the fi

RE: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

> > If you continue to use the SVN software a work-around to try and bypass > the race condition would be to retry the sqlite3_open after a short > pause when you intercept a CANTOPEN status. > JS > What is interesting here is that this error can happen at random moments (e.g during an insert, u

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

a flaw of sqlite and not a flaw of a 3rd party app)? Costas -Original Message- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Κυριακή, 4 Ιουνίου 2006 9:24 πμ To: sqlite-users@sqlite.org Subject: Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec If your

RE: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

that this is indeed a flaw of sqlite and not a flaw of a 3rd party app)? Costas > -Original Message- > From: John Stanton [mailto:[EMAIL PROTECTED] > Sent: Κυριακή, 4 Ιουνίου 2006 9:24 πμ > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Random error SQLITE_CANTOPEN on W

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

"Costas Stergiou" <[EMAIL PROTECTED]> wrote: > > I lately came upon a very strange error that occurs at random times. These kinds of problems are sometimes caused by virus scanners. Try turning off your virus scanner and see if the problem goes away. -- D. Richard Hipp <[EMAIL PROTECTED]>

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

anton [mailto:[EMAIL PROTECTED] Sent: Κυριακή, 4 Ιουνίου 2006 4:05 πμ To: sqlite-users@sqlite.org Subject: Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec You don't test for an error on your close statement. I suspect that the Sqlite databases are not being close

RE: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

is a really serious issue and, if it is not my fault, a show-stopper for winXP usage of SQLITE3. Costas > -Original Message- > From: John Stanton [mailto:[EMAIL PROTECTED] > Sent: Κυριακή, 4 Ιουνίου 2006 4:05 πμ > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Random erro

Re: [sqlite] Random error SQLITE_CANTOPEN on Windows XP SP2 with sqlite3_exec

You don't test for an error on your close statement. I suspect that the Sqlite databases are not being closed because activity is not finalized. Your error pops up when you have a very large number of databases open. JS Costas Stergiou wrote: Hello everyone, I lately came upon a very stra