On Jun 12, 2017 8:26 PM, "Keith Medcalf" <kmedc...@dessus.com> wrote:
Additionally, declaring NOT NULL or NULL is ignored. CHECK constraints are honoured. DEFAULT values are ignored. so CREATE TABLE x(id INTEGER NULL PRIMARY KEY CHECK (id>1000) DEFAULT (-1)); & CREATE TABLE x(id INTEGER NULL PRIMARY KEY CHECK (id>1000)); is CREATE TABLE x(id INTEGER PRIMARY KEY CHECK(id>1000)); This is because an "INTEGER PRIMARY KEY" has a computed default that you cannot override, and the rowid must always be always NOT NULL ... Thanks for the info. I'm assuming that the order of constraints is unimportant so check could come before PK. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
