I should add that a pragma that cause CHECK constraints to be automatically created for enforcing strong typing in subsequent CREATE TABLE statements is rather like having FOREIGN KEY clauses automatically generate triggers. There's precedent, in other words, and it is a simple way to implement strong typing.
Also, when you view the schema you'll see the CHECK clauses, and will know not only that typing is enforced at INSERT/UPDATE time, but also what type SQLite3 actually inferred from the declared type. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
