Populating Calibre DB with NON

[Darko]

Hi,
I am trying to develop a tool that coverts an existing database to calibre sqlite db.
However, the sqlite driver I am using in my .Net project chokes on the word "NON".
See following table examples from calibre source:
CREATE TABLE comments ( id INTEGER PRIMARY KEY,
book INTEGER NON NULL,
text TEXT NON NULL COLLATE NOCASE,
UNIQUE(book)
);
...
CREATE TABLE data ( id INTEGER PRIMARY KEY,
book INTEGER NON NULL,
format TEXT NON NULL COLLATE NOCASE,
uncompressed_size INTEGER NON NULL,
name TEXT NON NULL,
UNIQUE(book, format)
);
...

As far as I know SQL does not have keyword "NON".
Could anybody enlighten me regarding this construct?
Tnx.

[kovidgoyal]

the calibre database is sqlite, NON NULL is a constraint that will cause sqlite to raise an error if you try to set a null value for a field declared as non null.

[chaley]

You should use calibre to create the empty database. If you don't then it is likely that the DB version, the constraints, and the triggers won't be right.

[Darko]

Thanks for answering.
I know about constrains. However based on "http://www.sqlite.org/lang_keywords.html" there is no SQLite Keyword "NON" (although NOT NULL is ok).
Probably the designers of the driver followed this table.

[Darko]

Originally Posted by chaley

You should use calibre to create the empty database. If you don't then it is likely that the DB version, the constraints, and the triggers won't be right.

> You should use calibre to create the empty database.
Yes, that is exactly what I did.
However, during the testing I would like to open calibre db in VisualStudio and validate my tool with a unit test. But, as I said, sqlite driver could not get around constraint "NON" - and "NOT" works fine. Is there any difference between the two?

[kovidgoyal]

No difference as far as I know.

[kovidgoyal]

For consistency, I have changed all the NON NULLs to NOT NULLs

https://github.com/kovidgoyal/calibr...fa350817a362d4