This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Alex.LordThorsen
Recipients Alex.LordThorsen
Date 2014-04-16.07:52:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397634761.6.0.834429340049.issue21250@psf.upfronthosting.co.za>
In-reply-to
Content
In Lib/sqlite3/tests/dbapi.py there are no unit tests which test out sqlite3's 'insert or [algorithm].' These algorithms are also referred to as SQL 'insert on conflict.'

More details at,
https://www.sqlite.org/lang_conflict.html

Not having unit tests for these features, especially 'insert or rollback,' seems like an easy way for timing and threading bugs to get lost in the database api.
History
Date User Action Args
2014-04-16 07:52:41Alex.LordThorsensetrecipients: + Alex.LordThorsen
2014-04-16 07:52:41Alex.LordThorsensetmessageid: <1397634761.6.0.834429340049.issue21250@psf.upfronthosting.co.za>
2014-04-16 07:52:41Alex.LordThorsenlinkissue21250 messages
2014-04-16 07:52:40Alex.LordThorsencreate