On Jan 4, 2020, at 12:49 PM, Gerry Snyder <mesmerizer...@gmail.com> wrote: > > On Fri, Jan 3, 2020 at 10:57 AM Richard Watt <watt...@gmail.com> wrote: > >> Does anyone know of any potential issues I might encounter and how to >> correct them please? >> > Few packages are maintained with more care about backward compatibility > than SQLite. > > The best estimate for number of issues you will run into is Zero.
My largest application using SQLite has run into a few of them over the years. I ran into one just a month or so ago when we tried to slurp a legacy static SQL file into SQLite and it rejected it because we were relying on the double-quoted string misfeature and didn’t catch all of the uses of it when we followed the advice accompanying the 3.29.0 release to disable support for it. (Our main-line app code doesn’t use the misfeature, only this one canned SQL file that’s rarely used, thus the lag in discovery.) My advice is to try a blind upgrade, and if that fails, first try to find out why and use the ChangeLog referenced by J. King to find the reason, and if you can’t do that, then begin bisecting the change history. Halfway between current and 3.6.16 is the famous “pi” release (3.14), then halfway again is 3.22, and so on. There have been 116 releases (!) since 3.6.16, so the maximum number of releases you’ll have to try with a binary bisect is 7. No big. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
