On 17 May 2018, at 7:13pm, Dominique Devienne <ddevie...@gmail.com> wrote:
Advertising
> I think I'm not alone in wishing there was a way to disable all legacy > backward compatibility "warts". The testing involved is horrendous. You have to test everything with the setting enabled, then test it again with it disabled. If there are two such switches, the testing required is quintupled, if there are three, octupled. However, doing it properly might be how SQLite 4 would start -- by resetting all "historical compatibility" problems. Not only for understanding SQL, but _v2() calls, supporting old versions of the database format, and such stuff. It can also be stricter about rejecting bad SQL syntax or corrupted database files. And it doesn't have to compile on ancient versions of compilers. The interesting thing would be to find out how much code space this would save. It might be almost nothing. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
