On Wed, Feb 22, 2017 at 6:09 PM Dominique Devienne <ddevie...@gmail.com> wrote:
> On Wed, Feb 22, 2017 at 5:50 PM, Richard Hipp <d...@sqlite.org> wrote: > > 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. > [...] you can go back and figure out which constraint [...] > > > [...] Could we please at least have the constraint name? > [...] And that would make it consistent with the normal message > from an insert failure. Consistency is good right? --DD > I see this has been merged to trunk (w/o the constraint name). Thank you again. --DD _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
