On Sun, 20 Dec 2015 19:12:39 +0100
Big Stone <stonebig34 at gmail.com> wrote:
> Best whishes for 2016!
If it's not too late to join the party...
1. create table T (t primary key);
update T set t = t+1;
for consecutive values of t.
2. Specific constraint references in error messages.
3. Correct math. E.g.:
$ sqlite3 db 'select typeof(1/0)'
typeof(1/0)
-----------
null
should produce an error. There are other examples, but none comes to
mind just now.
I would like to see a strict mode, too. I would also like to be able
to make "strictness" a property of the database, not the connection.
One way to do that would be to honor a special user-created table, say
"PRAGMAS", with name-value pairs that are automatically applied when
the database is opened.
IMHO update isolation (#1) and mathematical correctness (#3) are
prerequisites for analytical functions. SQLite can't be dependably
used for quantitative work if domain errors are silently ignored.
--jkl
