Thank you, INTEGER -> INT solved the problem. According to manual, this will make search slower, but I give data integrity more weight for now.
Roman ________________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Igor Tandetnik [i...@tandetnik.org] Sent: Monday, May 20, 2013 4:41 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] autoincrement and primary key On 5/20/2013 4:17 PM, Roman Fleysher wrote: > I would like to use INTEGER PRIMARY KEY, but I would like to disable its > implicit AUTOINCREMENT feature. Namely, if INSERT specifies value of the > column, I would like uniqueness to be enforced, but if NULL is supplied, I > would like the operation to fail instead of advancing key to a new integer. Just make the column "INT PRIMARY KEY NOT NULL" (note INT rather than INTEGER). This way, it is not an alias for ROWID but a column in its own right, and doesn't get assigned a value automatically. -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
