[issue22382] sqlite3 connection built from apsw connection should raise IntegrityError, not DatabaseError

2014-09-18 Thread william tonkin
Changes by william tonkin : -- nosy: +ghaering ___ Python tracker <http://bugs.python.org/issue22382> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22382] sqlite3 connection built from apsw connection should raise IntegrityError, not DatabaseError

2014-09-11 Thread william tonkin
william tonkin added the comment: The following worked for me: --- util.c 2014-09-11 15:15:11.480266548 -0400 +++ util.c.fixed2014-09-11 15:17:19.214878592 -0400 @@ -54,7 +54,7 @@ (void)sqlite3_reset(st); } -errorcode = sqlite3_errcode(db); +errorcode

[issue22382] sqlite3 connection built from apsw connection should raise IntegrityError, not DatabaseError

2014-09-11 Thread william tonkin
william tonkin added the comment: sqlite3 allows a connection to be built from an apsw.Connection(). Using an apsw.Connection() to build an sqlite3.connect() implies that the underlying sqlite database engine will have extended error codes turned on (the default if for them to be turned off

[issue22382] sqlite3 connection built from apsw connection should raise IntegrityError, not DatabaseError

2014-09-10 Thread william tonkin
New submission from william tonkin: python Python 2.7.6 (default, Dec 23 2013, 13:16:30) [GCC 4.1.2 20080704 (Red Hat 4.1.2-54)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> - test script - i