On 2014/03/27 02:30, Richard Hipp wrote:
On Wed, Mar 26, 2014 at 8:12 PM, RSmith <[email protected]
<mailto:[email protected]>> wrote:
In your case it does so using SQLite version 3.8.2 while you have the other
app you are making write to the same DB using
SQLite 3.6.17... I'm surprised you have not corrupted the DB yet,
It is possible to create a database using 3.8.2 that is not usable in 3.6.17, but adding features (such as partial indices) that
are not available in 3.6.17. But that is not quite the same as "corrupting" the database. If 3.6.17 can read and write the
database, then it won't hurt it. If the database uses features that 3.6.17 doesn't understand, then it will refuse to change it,
and the database will survive unharmed.
Thanks for the clarification, this is quite a good feature of SQLite. So to be sure, the worst the OP could do is add something via
his external tools that might render the Database unreadable by the program using the lesser version of SQLite, but in no case would
that DB be corrupted, i.e. version 3.8.2 would always be able to open it again.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
