After looking into error messages further, I see that the constraint name is not included in NOT NULL or UNIQUE constraint errors although it is there in CHECK constraint errors. The table.column that caused the error is in the messages so it is possible to identify which column caused the error. I'm guessing the constraint name is there for CHECK errors because there can be more than one of them for a column so the column name doesn't uniquely identify which check failed.
Since constraint names don't seem to turn up anywhere except CHECK constraint errors, is there any point in defining them? Pete -- View this message in context: http://sqlite.1065341.n5.nabble.com/Foreign-Key-errors-tp75473p75602.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users