This is as much out of curiosity as anything. I know that to get the rowid aliasing behavior for a table one must define the column type as INTEGER and using the constraint PRIMARY KEY. Something like:
CREATE TABLE A(B INTEGER PRIMARY KEY); In testing this afternoon I was curious if I could give the constraint a name: CREATE TABLE A(B INTEGER CONSTRAINT B_PK PRIMARY KEY); I can, and it is still an alias of the rowid. If I change the type to INT then it is not an alias. This all makes sense. If I insert NOT NULL between the type and PK constraint, it still is an alias (as long as the type is INTEGER). Is it fair to say that the rowid aliasing behavior does not require (by design) the incantation "INTEGER PRIMARY KEY" (all three words in that order as the "type") as long as the type is INTEGER and the constraint PRIMARY KEY appears somewhere in the column's constraint list? -- Scott Robison _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
