Well, I'm stuck. If I use the CLI I get: D:\dev\SQLite\3_4_1\Bin>sqlite3 myproj.db SQLite version 3.4.1 Enter ".help" for instructions sqlite> pragma synchronous=0; SQL error: database is locked sqlite> .quit
However, I find I can copy the database and journal and do the same thing on the copy and everything works perfectly (journal file disappears). It would appear something does have a lock on the original file. I've moved it twice to different directories (to ensure my app, which isn't running, can't find it). I've rebooted twice (it's Windows), and run SysInternal's Handle app which shows all open files, and this file isn't open by anything. Renaming the original also has no effect. Can a file lock survive a reboot? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 19, 2007 11:07 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Trying to understand SQLITE3_BUSY > > "Doug" <[EMAIL PROTECTED]> wrote: > > I have a database file that was created with version 3.4.1. It _may_ have > > been written to at some point with 3.5.3 - can't say for sure. At some > > point a transaction was started and the app was stopped (probably me in the > > debugger). I assume I was using 3.4.1 at the time it but it could > > potentially have been 3.5.3 (working with two different code bases on and > > off). > > > > > > > > So at this moment I have in the directory: > > > > Myproj.db > > > > Myproj.db-journal > > > > Can you open and view the database in the CLI? > > -- > D. Richard Hipp <[EMAIL PROTECTED]> > > > ---------------------------------------------------------------------------- - > To unsubscribe, send email to [EMAIL PROTECTED] > ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
