[issue12997] sqlite3: PRAGMA foreign_keys = ON doesn't work

2011-10-17 Thread Mark Bucciarelli
Changes by Mark Bucciarelli : -- resolution: -> invalid ___ Python tracker <http://bugs.python.org/issue12997> ___ ___ Python-bugs-list mailing list Unsubscri

[issue12997] sqlite3: PRAGMA foreign_keys = ON doesn't work

2011-10-16 Thread Mark Bucciarelli
Mark Bucciarelli added the comment: BAD : sqlite3.sqlite_version_info = (3, 6, 12) GOOD: sqlite3.sqlite_version_info = (3, 7, 4) GOOD: sqlite3.sqlite_version_info = (3, 7, 8) I guess this is the cause of the different behavior. sqlite_version_info is the version of the underlying sqlite3

[issue12997] sqlite3: PRAGMA foreign_keys = ON doesn't work

2011-10-15 Thread Mark Bucciarelli
Mark Bucciarelli added the comment: Something strange is going on. I just built pysql 2.6.3 from source, and now my unit test gives the expected "IntegrityError: foreign key constraint failed" message. poq, what do you get when you run this script: import sqlite3 print "sqlit

[issue12997] sqlite3: PRAGMA foreign_keys = ON doesn't work

2011-09-17 Thread Mark Bucciarelli
Mark Bucciarelli added the comment: huh. is it already on in your sqlite install? $ sqlite3 SQLite version 3.7.7.1 2011-06-28 17:39:05 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> pragma foreign_keys; 0 sqlite>

[issue10740] sqlite3 module should allow DDL statements in transactions

2011-09-17 Thread Mark Bucciarelli
Mark Bucciarelli added the comment: Opened http://bugs.python.org/issue12997 in case there is a way to solve the foreign_key PRAGMA issue with a less disruptive fix. -- nosy: +Mark.Bucciarelli ___ Python tracker <http://bugs.python.org/issue10

[issue12997] sqlite3: PRAGMA foreign_keys = ON doesn't work

2011-09-16 Thread Mark Bucciarelli
New submission from Mark Bucciarelli : If I read http://bugs.python.org/issue10740#msg132470 correctly, the foreign_keys PRAGMA is a no-op b/c "The python sqlite module automatically commits open transactions when it encounters a DDL statement." Entering as a separate issue as I&