Hmm, it didn't help. I can still easily reproduce the TortoiseSVN bug.
The only reliable workaround is to use different journal_mode (or
implementing renaming of the journal file before deleting it).
Best regards,
F.
On Wed, Oct 15, 2008 at 2:33 PM, Shane Harrelson <[EMAIL PROTECTED]> wrote:
> Ve
Version 3.6.1 (IIRC) had changes to improve the error detection and retry
logic for this condition (typically caused when a 3rd party application
opens the SQLite journal file.)
HTH.
-Shane
On Mon, Oct 13, 2008 at 12:52 PM, Doug <[EMAIL PROTECTED]> wrote:
> I'm using SQLite 3.5.6 on Windows and
http://www.mail-archive.com/sqlite-users@sqlite.org/msg34453.html
On Mon, Oct 13, 2008 at 6:52 PM, Doug <[EMAIL PROTECTED]> wrote:
> I'm using SQLite 3.5.6 on Windows and intermittently get SQLITE_CANTOPEN
> when doing an insert. When that fails, I can use the debugger to go back up
> and step th
Stephen Oberholtzer wrote:
On Mon, Oct 13, 2008 at 12:52 PM, Doug <[EMAIL PROTECTED]> wrote:
I'm using SQLite 3.5.6 on Windows and intermittently get SQLITE_CANTOPEN
when doing an insert. When that fails, I can use the debugger to go back
up
and step through the same lines again (using the
On Mon, Oct 13, 2008 at 12:52 PM, Doug <[EMAIL PROTECTED]> wrote:
> I'm using SQLite 3.5.6 on Windows and intermittently get SQLITE_CANTOPEN
> when doing an insert. When that fails, I can use the debugger to go back
> up
> and step through the same lines again (using the same database handle -
>
I'm using SQLite 3.5.6 on Windows and intermittently get SQLITE_CANTOPEN
when doing an insert. When that fails, I can use the debugger to go back up
and step through the same lines again (using the same database handle -
nothing opened or closed in between) and it will work.
I am using sqlite3_bi
6 matches
Mail list logo