On 23/06/16 16:08, Richard Hipp wrote:
On Thu, Jun 23, 2016 at 9:54 AM, Mark Brand <mabr...@mabrand.nl> wrote:
Hi,
Just wondering about the apparent variation among sqlite3 versions and/or
configurations with respect to the "no such table" error. In some cases
it's enforced at view creation and in others at execution.
https://www.sqlite.org/releaselog/3_9_0.html
Version 3.9.0 is backwards compatible with 3.8.11, but not forwards
compatible. In other words, if it works in 3.8.11 it will also work in
3.9.0 and later. But some things work in 3.9.0 and later which are not
recognized by 3.8.11 and before.
Thanks. I'm curious about the thinking behind this change. What are the
benefits that offset the increased risk that a particular database will
seem to have been created correctly only to fail at runtime? I'm not
complaining, just curious.
Mark
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
