On 2 Apr 2017, at 2:50pm, David Burgess <dburg...@gmail.com> wrote: > I have a table with 500,000 rows, it has a unique column of registration > numbers > The rules for the format of these numbers has changed over time and the > schema has changed with the rules of the time. PRAGMA integrity_check > now complains about some rows not passing the constraint. > An option on integrity_check to ignore schema CHECK would be avoid having > to code a CHECK that caries with time.
Remove the CHECK constraint from the table. Do your checking using a TRIGGER. When your format changes, update the TRIGGER. This will not invalidate rows which are already in the table. > I preferred the pre 3.18 behaviour. More flexible and fulfills a real > world requirement. But wrong. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
