Hello,
as the author of yet another SQLite3 binding for a manifestly typed
language (CHICKEN Scheme) I can only second the concerns expressed in
other answers to the original posting. I would expect the interface to get
far more complicated with strict typing in SQLite3. In fact, that SQLite3
is manifestly typed was one of the main reasons for choosing it as a
database backend in my Scheme applications in the first place.
I also do not understand why the absence of NULL should be helpful for the
database user. It may be helpful for the efficient implementation of the
database, but SQLite3 already does a pretty good job there.
I suppose that the definition of custom datatypes would add a large amount
of complexity to the database. And in the rare cases that I really need
something like a seperate type, I can usually use a BLOB and a few custom
functions.
What I do like about the proposal is the addition of a boolean datatype,
though. That would make the interface more convenient for some of the
scripting languages that have such a type.
cu,
Thomas
- Re: [sqlite] updating SQLite to implement The Third Manifest... Thomas Chust
-
