On 12 Aug 2019, at 6:01pm, Thomas Kurz <sqlite.2...@t-net.ruhr> wrote:
>> This would break backward compatibility. It is necessary to be sure that >> database files made with current versions of SQLite can be opened with old >> versions back to 2013. > > This is what I would call "forward compatibility": You expect an old > application to be able to read file formats of a future version. Do you have > an example where there is really required? A programmer uses a copy of the SQLite CLI to correct errors in a database made and maintained by a production program. This involves making a new table, copying some data from the old data to the new table, deleting the old table, then renaming the new table. When the programmer is finished making changes, they replace the old version of the database with the corrected version. The production program, written three years ago, uses an old version of the SQLite library. The editing happens on the programmer's own computer which, naturally, has an up-to-date copy of the SQLite CLI, with an up-to-date copy of the SQLite library. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
