Re: [sqlite] Ticket 3810: SQLITE_ERROR on concurrent CREATE TEMP TRIGGER and sqlite3_close()

2009-10-21 Thread Dave Toll
te] Ticket 3810: SQLITE_ERROR on concurrent CREATE TEMP TRIGGER and sqlite3_close() -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Toll wrote: > Could you point me to the test case you referred to? Look near the bottom of the ticket where it lists the various checkins. [6955] is the te

Re: [sqlite] Ticket 3810: SQLITE_ERROR on concurrent CREATE TEMP TRIGGER and sqlite3_close()

2009-10-20 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Toll wrote: > Could you point me to the test case you referred to? Look near the bottom of the ticket where it lists the various checkins. [6955] is the test case. You can examine the current source in case that has changed at

Re: [sqlite] Ticket 3810: SQLITE_ERROR on concurrent CREATE TEMP TRIGGER and sqlite3_close()

2009-10-20 Thread Dave Toll
on concurrent CREATE TEMP TRIGGER and sqlite3_close() -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Toll wrote: > The race condition described in http://www.sqlite.org/cvstrac/tktview?tn=3810 > is > still present in SQLite 3.6.19 (amalgamation version running on Linux) My bigges

Re: [sqlite] Ticket 3810: SQLITE_ERROR on concurrent CREATE TEMP TRIGGER and sqlite3_close()

2009-10-19 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Toll wrote: > The race condition described in http://www.sqlite.org/cvstrac/tktview?tn=3810 > is > still present in SQLite 3.6.19 (amalgamation version running on Linux) My biggest problem with the ticket is the huge list of omits and other

[sqlite] Ticket 3810: SQLITE_ERROR on concurrent CREATE TEMP TRIGGER and sqlite3_close()

2009-10-19 Thread Dave Toll
Hello list I'm posting here as my ticket was recently closed. The race condition described in http://www.sqlite.org/cvstrac/tktview?tn=3810 is still present in SQLite 3.6.19 (amalgamation version running on Linux) - the source code used to reproduce this issue has not changed and is still