On 12/30/2016 5:25 PM, Stephen Chrzanowski wrote:
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
On 12/29/2016 9:20 PM, Richard Hipp wrote:
On 12/30/16, Bennett Haselton wrote:
Presumably it's not possible for a tool to output a detailed message
like "Your file was generated by SQLite library version 3.6.2, but this
tool only supports versions up to 3.5.1",
OK. I have
? There can be lots of reasons that a file is not parseable, so how
the tool supposed to tell the difference between "This file is corrupt"
and "This file is too new for me to read"?
Bennett
On 12/29/2016 5:32 PM, Richard Hipp wrote:
On 12/29/16, Bennett Haselton wro
Yesterday I spent some time trying to solve a SQLite problem that turned
out to be due to using an old version of sqlite3, so that when I tried
to open a database created with a newer SQLite library, it would output
"Error: file is encrypted or is not a database". Later I found out this
was be
4 matches
Mail list logo
