4 Commits

Author	SHA1	Message	Date
drh	a690ff360b	Change the error message text for SQLITE_ERROR to omit the part about ... "missing database" as that meaning is now obsolete (since approx SQLite 2.0). FossilOrigin-Name: 732f90d6327c5c6368fc8b4cc207bd644ef08e3ae6d2e7295258ab099deaba63	2017-07-07 19:43:23 +00:00
drh	f9c8ce3ced	Standardize the error messages generated by constraint failures to a format ... of "$TYPE constraint failed: $DETAIL". This involves many changes to the expected output of test cases. FossilOrigin-Name: 54b221929744b1bcdbcc2030fef2e510618afd41	2013-11-05 13:33:55 +00:00
drh	433dccfb52	Rename SQLITE_CONSTRAINT_RAISE to SQLITE_CONSTRAINT_TRIGGER. Put the ... extended constraint error codes in alphabetical order. Add many test cases for the extended constraint error codes. FossilOrigin-Name: 3f67437536591a1b0742a25b983707933aaa16d5	2013-02-09 15:37:11 +00:00
dan	029ead645d	If an error occurs within sqlite3_step() on a statement prepared using sqlite3_prepare_v2(), transfer both the error code and error message to the database handle before sqlite3_step() returns (so that they are available via sqlite3_errcode() and sqlite3_errmsg(). Prior to this commit, only the error code was transfered. The error message was not available until after either sqlite3_reset() or sqlite3_finalize() had been called on the statement handle. ... FossilOrigin-Name: 8f88cc4e616b4b30ed349f89e148f782da5cb6c4	2011-10-27 15:19:58 +00:00