Re: [sqlite] test/exists.test 2.$tn.1 fails if both DBs are in WAL mode

>> For me, this test from test/exists.test fails if both database >> connections are opened in WAL mode, that is if "PRAGMA journal_mode=WAL" >> is issued right after each DB is opened. >> >># TABLE objects. >># >>do_test { >> sql1 { DROP TABLE IF EXISTS t1 } >>

[sqlite] test/exists.test 2.$tn.1 fails if both DBs are in WAL mode

For me, this test from test/exists.test fails if both database connections are opened in WAL mode, that is if "PRAGMA journal_mode=WAL" is issued right after each DB is opened. # TABLE objects. # do_test{ sql1 { DROP TABLE IF EXISTS t1 } sql2 { CREATE TABLE t1(x) } sql1

Re: [sqlite] test/exists.test 2.$tn.1 fails if both DBs are in WAL mode

The test passes well if I recreate the database file anew just prior to running it so it acts upon an empty database. If this is what is intended, I apologize for the false alarm. Ralf On 10.04.2011 10:28, Ralf Junker wrote: > For me, this test from test/exists.test fails if both database >

[sqlite] test/exists.test 2.$tn.1 fails if both DBs are in WAL mode

For me, this test from test/exists.test fails if both database connections are opened in WAL mode, that is if "PRAGMA journal_mode=WAL" is issued right after each DB is opened. # TABLE objects. # do_test{ sql1 { DROP TABLE IF EXISTS t1 } sql2 { CREATE TABLE t1(x) } sql1