[EMAIL PROTECTED] wrote:
Dennis Cote <[EMAIL PROTECTED]> wrote:
It is worth noting that SQLite's behavior is not completely consistent.
If the column is declared to be an 'integer primary key', then SQLite
will insert a "default" value even when the user explicitly supplies a
NULL value in an insert statement.
Remember that PRIMARY KEY implies NOT NULL.
--
D. Richard Hipp <[EMAIL PROTECTED]>
Yes it does, so to follow the letter of the law, SQLite should throw an
error when the user tries to insert a NULL into an "integer primary key"
column. It doesn't do that, and I don't think it should be changed either.
I was just pointing out that a NULL doesn't always get inserted just
because the user EXPLICITLY entered that value in an insert statement as
was suggested by Derrell and others.
Dennis Cote
