Message 249010 - Python tracker

Message249010

Author	ghaering
Recipients	danielsh, ezio.melotti, ghaering, levkivskyi, sleepycal, torsten
Date	2015-08-23.16:16:32
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1440346593.11.0.554108565538.issue16379@psf.upfronthosting.co.za>
In-reply-to

Content
I propose to also set the SQLite extended error code if this is implemented. What's the reasoning behind offering a error code to name mapping? This seem problematic to me. In case a newer SQLite version introduces a new error code, this error code cannot be found in the mapping. I propose to leave this out in order to not have this problem. Otherwise we will have people depending on any error code being able to be found in this mapping.

Content

I propose to also set the SQLite extended error code if this is implemented.

What's the reasoning behind offering a error code to name mapping? This seem problematic to me. In case a newer SQLite version introduces a new error code, this error code cannot be found in the mapping. I propose to leave this out in order to not have this problem.

Otherwise we will have people depending on any error code being able to be found in this mapping.

History
Date	User	Action	Args
2015-08-23 16:16:33	ghaering	set	recipients: + ghaering, ezio.melotti, torsten, sleepycal, danielsh, levkivskyi
2015-08-23 16:16:33	ghaering	set	messageid: <1440346593.11.0.554108565538.issue16379@psf.upfronthosting.co.za>
2015-08-23 16:16:33	ghaering	link	issue16379 messages
2015-08-23 16:16:32	ghaering	create