On 2/22/17, Dominique Devienne <ddevie...@gmail.com> wrote: > > Could we please have the CHECK constraint name, > in addition to the table name, in case of a failure? > > Pushing my luck a little bit: any chance to be able to pinpoint the > offending rows, similar to how foreign_key_check does it?
CHECK constraint failures are suppose to be exceedingly rare. Elaborate error messages that pinpoint the problem are possible, but they increase the library complexity and footprint unnecessarily. In the rare event that you encounter a CHECK constraint failure, you can go back and figure out which constraint and which row is at fault using ordinary queries. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
