If the 3.1 file is created with the auto-vacuum option enabled
("PRAGMA auto_vacuum = 1;"), then the database will appear read-only
to 3.0 clients. That's the only incompatibility.
OK -- can auto-vacuum be turned on within a database that was created with 3.0?
b.bum
smime.p7s
Description: S/MIME cryptographic signature
