On Thu, Mar 7, 2013 at 11:12 AM, Ryan Johnson <ryan.john...@cs.utoronto.ca> wrote: > I would argue that, if a column has type affinity, CHECK should work with > the value that would actually get stored, not the one that was assigned.
But then you couldn't check the value that was attempted to store. You'd be stuck with dynamic type conversions in all cases. Anyways, think of CHECK constraints as equivalent to BEFORE INSERT/UPDATE triggers. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
