On Wed, Sep 9, 2015 at 3:56 PM, Baruch Burstein <bmburstein at gmail.com> wrote:
> Question in the subject > > -- > > ?Answered on the SQLite web site: http://sqlite.org/lang_createtable.html <quote> According to the SQL standard, PRIMARY KEY should always imply NOT NULL. Unfortunately, due to a bug in some early versions, this is not the case in SQLite. Unless the column is an INTEGER PRIMARY KEY <http://sqlite.org/lang_createtable.html#rowid> or the table is a WITHOUT ROWID <http://sqlite.org/withoutrowid.html> table or the column is declared NOT NULL, SQLite allows NULL values in a PRIMARY KEY column. SQLite could be fixed to conform to the standard, but doing so might break legacy applications. Hence, it has been decided to merely document the fact that SQLite allowing NULLs in most PRIMARY KEY columns. </quote>? -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown
