In a test harness, I'm using a sqlite3_prepare/bind/step/finalize sequence to add rows to a table, and then add them again, intentionally violating the unique index constraints. It appears that sqlite3_step reports the violation (sqlite3_errorMessage), and then the details (the offending column numbers) are only reported when I check the error in the sqlite3_finalize() routine ...
::: Error ::: sq3_step: Error 19 returned from sqlite3_step. constraint failed ::: Error ::: sq3_finish: Error 19 returned from sqlite3_finalize. columns sname, fname, dob are not unique This is not a problem, per se, but in an ideal world, one might handle the error one time, and receive all the relevant information at one go. Is there a reason to defer reporting the details until the transaction is completed? Just wondering ... Cheers, Rob Sciuk _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
