[EMAIL PROTECTED] wrote:
"Doug" <[EMAIL PROTECTED]> wrote:
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
"Doug" <[EMAIL PROTECTED]> wrote:
> Thank you Richard.
>
> I have full rights to that directory tree and to the main database file, but
> it turns out the journal was created by a service, and so the journal was
> only writable by the service account.
> That solved it.
>
> Thanks again --
:)
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 19, 2007 12:49 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Trying to understand SQLITE3_BUSY
>
> "Doug" <[EMAIL PROTECTED]> wrote:
> > Well, I'
"Doug" <[EMAIL PROTECTED]> wrote:
> 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
gt; 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 sa
"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
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
7 matches
Mail list logo
