What the SQL standard calls an "exception" is not necessarily exactly
the same as an exception in other programming languages.
Granted.
If SQLite were to change the division-by-zero handling, it could be
reported exactly like most other errors, by returning SQLITE_ERROR from
sqlite3_step().
It could as well deliver +/- Inf or Nan.
select 15 % 'abc' returns null as well.
Integer overflow could also raise some new SQLite-level error.
SQLite string functions could also raise new errors when invalid
indices are provided, like substr("abc", 456, 17) which doesn't make
any sense.
All in all I don't see any serious enough reason to change behaviors at
this stage.
Complaints posted here about these error situations being kept silent
are rather rare.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
