On Sun, 10 Mar 2019 17:04:46 -0400 "James K. Lowden" <[email protected]> wrote:
> Why does the .import command cause the CHECK constraint to fail, when > an ordinary INSERT does not? On Sun, 10 Mar 2019 14:12:33 -0700 Shawn Wagner <[email protected]> wrote: > The check constraint is probably being evaluated (with t as a string) > before any type conversion to match the column affinity is done. Does anyone have a better answer? Isn't .import supposed to work like INSERT? If it doesn't, CHECK constraints for type safety are useless for tables that are loaded from files. --jkl _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
