On Wed, Dec 12, 2012 at 3:36 PM, Richard Hipp <d...@sqlite.org> wrote:
> On Wed, Dec 12, 2012 at 2:29 PM, Levi Haskell (BLOOMBERG/ 731 LEXIN) < > lhask...@bloomberg.net> wrote: > >> My suggestion would be to have check_integrity command verify referential >> integrity as well only if it's executed while the foreign key enforcement >> is enabled on the connection. >> > > This seems like a reasonable request. And while we are at it, we will > likely also verify UNIQUE and CHECK constraints too. > By the way, verifying foreign key constraints is trickier than it seems at first glance, because you have to make sure to get it right for cases involving NULLs and differing collating sequences and affinities between parent and child tables. > > PRAGMA quick_check is still available for users who do not want to take > the extra overhead of verifying UNIQUE, CHECK, and foreign key constraints. > > Does anybody know of any reason why we should not do this? > > > -- > D. Richard Hipp > d...@sqlite.org > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
