IMO, the responsibility of checking database versions should be owned by the application, not the library. The logic that the application can or cannot, should or should not use the database is an application decision. If the library just were to provide what version of SQLite made or last modified the DB would be sufficient, but, having the library itself throw an exception/warning/error/fail/[anything beyond provisions for the database version] is going beyond what the library should be doing.
On Fri, Dec 30, 2016 at 2:31 PM, Bennett Haselton <bennetthasel...@gmail.com > wrote: Thanks. My other suggestion was that if you open a database file with a > *newer* version of the library than the one that was used to create it, you > can also warn, "This file was created using SQLite version a.b.c, but > you're attempting to save it in format SQLite version x.y.z. If you save > changes to this file, it may no longer be compatible with the program that > generated it." > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
