On Wed, Feb 22, 2017 at 4:47 PM, Richard Hipp <d...@sqlite.org> wrote:
> On 2/22/17, Dominique Devienne <ddevie...@gmail.com> wrote:
> > Neither {{pragma integrity_check}} nor {{pragma foreign_check_check}}
> > checks CHECK constraints.
>
> That is now fixed on a branch. I am still testing the changes prior
> to merging onto trunk.
Thanks Richard!
Could we please have the CHECK constraint name,
in addition to the table name, in case of a failure?
Similar to how we get that name on insert in case of a failure.
(Personally I'd prefer to have both the CHECK name and the TABLE name,
instead of one or the other, depending on whether the constraint is named
or not).
zErr = sqlite3MPrintf(db, "CHECK constraint failed in %s",
pTab->zName);
Pushing my luck a little bit: any chance to be able to pinpoint the
offending rows, similar to how foreign_key_check does it?
I guess one can manually grab the CHECK constraint from sqlite_master,
and do a select on the table to find those rows,
that just not very convenient :).
Thanks, --DD
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
