Hello ! Thanks for reply !
I still think that is worth having warnings for the already known quirks on sqlite, probably even show it to stderr when building in debug mode because I believe at some point people will do some debugging. Or maybe even better having a pragma "PRAGMA check_valid_sql_statements=ON" and add a note on the documentation to developers to try at least once before deploy and or in development mode to be sure they have clean/valid sql statements. It probably will not clean all existing code but I believe it can gradually improve the situation. Cheers ! > Sat Sep 05 2015 11:16:26 am CEST CEST from "Simon Slavin" ><slavins at bigfraud.org> Subject: Re: [sqlite] Third test of json and index >expressions, now it works > > On 5 Sep 2015, at 10:07am, Domingo Alvarez Duarte ><sqlite-mail at dev.dadbiz.es> wrote: > > >>What about the warning messages to stderr through sqlite3 when opening >> databases with invalid sql constructions, this way we can gradually have >>less >> and less code written in a non compliant way. >> > It might be acceptable to put warning code in sqlite3.exe and its >equivalents for other platforms. But the majority of SQLite installation are >on things which are not personal computers: mobile phones, GPS units, Digital >TV boxes, etc.. They don't have stderr. They don't even have stdout. > > Also I don't think it's worth doing at all. The developers are currently >playing with SQLite4 which does not have to support the same level of >backward compatibility as SQLite3. It can just refuse to parse commands which >the development team does not wish to support. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > ?
