Ahh being dull and in a hurry thanks
Paul www.sandersonforensics.com skype: r3scue193 twitter: @sandersonforens Tel +44 (0)1326 572786 http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit -Forensic Toolkit for SQLite email from a work address for a fully functional demo licence On 18 May 2017 at 17:26, Gwendal Roué <gwendal.r...@gmail.com> wrote: > > > Le 18 mai 2017 à 18:16, Paul Sanderson <sandersonforens...@gmail.com> a > écrit : > > > > Is this a bug? > > > > Create table test (id integer not null primary key, data text); > > insert into test values (null, 'row1'); > > select * from test; > > 1, row1 > > > > I know that if you provide a NULL value to a column define as integer > > primary key that SQLite will provide a rowid, but should the not null > > constraint be obeyed? > > Hello Paul, > > The constraint is obeyed, since there is no NULL values in the database. > > To put it in another way: constraints are properties of the *database > content*, not of the *operations* on content. They're static, not dynamic. > > That's why constraints can be checked with PRAGMA > schema.foreign_key_check, which tells if the current state of the database > content is valid. > > That's also why the insert statement above succeeds, as long as the value > that is eventually inserted in the database is NOT NULL. > > Gwendal Roué > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
