Hello,
I’ve got a set of python 3 unittests which use sqlite (versions 3.12.0 and
3.13.0 under Linux 4.4.6-gentoo x86_64).
There is one test which closes the database and opens it again during the test.
If I use the WAL (by using conn.execute("PRAGMA journal_mode=WAL;")) and run
all unittests, this unittest produces a database file with the empty schema
after first close, so it fails.
When I run it alone (or without WAL), it passes.
I’ve checked “hexdump -C” of the normal and the bad cases after first close, in
both cases the size of database file is the same, they contain common data for
inserted rows, but there is no “CREATE TABLE ...” statements in the bad
database file.
There are conn.commit() calls after each modification SQL statement. I even
tried to put explicit "BEGIN; ... COMMIT;" around "CREATE TABLE IF NOT
EXISTS..." statements, it doesn't help.
Is it a well-known problem ?
Regards,
Max
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
