Hi Shane!

I used two separate builds. One was built with the following command line:

cl /DSQLITE_ENABLE_FTS3=1 /DSQLITE_ENABLE_COLUMN_METADATA=1
/DTHREADSAFE=1 /O2 /LD sqlite3.c sqlite3.def

and the other was built from inside Visual Studio 2010 UI and reports
the following compile options:

sqlite> select sqlite_source_id();
2010-07-09 12:57:54 0c32c4bbdd74297767dcf4ec4295f9cc72875af0
sqlite> PRAGMA compile_options;
DEBUG
ENABLE_COLUMN_METADATA
ENABLE_FTS3
TEMP_STORE=1
THREADSAFE=1

Both suffer from the same problem and I tested it on various different
database files.

The reason why you probably can't reproduce it is because the problem
manifests only when other application blocks access to the journal
file. In my case the other application is TortoiseSVN, specifically
the TSVNCache process. In fact that was the original reason why we
started using journal_mode=truncate, which was supposed to avoid
deleting the journal file, but for some reason the new SQLite version
tries to do it anyway while the older one didn't.

Best regards,
Filip Navara

On Tue, Jul 13, 2010 at 11:21 PM, Shane Harrelson <sh...@sqlite.org> wrote:
> I tried to reproduce the issue with the latest version, as well as with the
> referenced snapshot, and could not.
> I ran two instances of the sqlite CLI as you indicated without issue.
>
> C:\work\sqlite\win32\Debug>sqlite_snapshot test.db
> SQLite version 3.7.0
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> pragma encoding="UTF-8";
> sqlite> pragma auto_vacuum=incremental;
> sqlite> pragma journal_mode=truncate;
> truncate
> sqlite> select sqlite_version();
> 3.7.0
> sqlite> select sqlite_source_id();
> 2010-07-09 12:57:54 0c32c4bbdd74297767dcf4ec4295f9cc72875af0
> sqlite> PRAGMA compile_options;
> DEBUG
> OMIT_LOAD_EXTENSION
> TEMP_STORE=1
> TEST
> THREADSAFE=1
> sqlite>
>
> I included the output of version, source_id, and compile_options for
> reference.
>
> What options are you compiling with?  Is there perhaps a journal file
> somewhere that you're unaware of?
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to