On Wed, Mar 26, 2014 at 8:12 PM, RSmith <rsm...@rsweb.co.za> 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. It would be good for the application to move to 3.8.2 (or 3.8.4.2) which is faster and more reliable than 3.6.17. But there is no serious risk of corrupting the database just by using 3.6.17. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
