On 12/21/2017 12:50 PM, Simon Slavin wrote:
SQLite version 3.19.3 2017-06-27 16:48:08
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> CREATE TABLE MyTable (a INTEGER, CONSTRAINT noless CHECK (a > 10));
sqlite> INSERT INTO MyTable VALUES (15);
sqlite> INSERT INTO MyTable VALUES (5);
Error: CHECK constraint failed: noless
sqlite> INSERT OR IGNORE INTO MyTable VALUES (6);
sqlite> SELECT * FROM MyTable;
15
sqlite>
What the hell ? Why does that work ? Isn’t it a huge bug ? How did you
discover it ?
My understanding is that using INSERT OR IGNORE meant that bad inserts would
fail, but they would do so silently, without triggering an error result.
Isn't that precisely what happened in your example? Inserting 6 failed
silently. What again seems to be the problem?
If I understand correctly, "the IGNORE resolution algorithm skips the one row that
contains the constraint violation and continues processing subsequent rows of the SQL
statement as if nothing went wrong" means that a row that violates constraints will
not be inserted.
And in your example, it was not.
--
Igor Tandetnik
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
