Thanks for addressing this, Richard.
Preset the legacy_file_format pragma to the value of the
primary database so that a VACUUM will not unknowingly
alter the setting. Ticket #2804.
http://www.sqlite.org/cvstrac/chngview?cn=4574
Could you please update the PRAGMA documentation to reflect t
When I compare the database bytes before and after the 2nd
process VACUUM these bytes differ:
zero-basedvalue value
byte offset beforeafter my guess of what it is
2nd VAC 2nd VAC
--- --- --- --
272 5
Regarding http://www.sqlite.org/cvstrac/tktview?tn=2804 ...
I'm confused by the explanation.
Ignoring the PRAGMA for the moment, I was surprised that DESC
indexes were not available after a reconnect and VACUUM, as shown
in the example:
$ rm -f foo.db
$ ./sqlite3-3.5.3.bin foo.db
SQLite version
3 matches
Mail list logo