Public bug reported:
The recently merged changes to use journal_mode=WAL and adding some
columns to event_view requires schema upgrades.
1) Setting WAL journalling *permanently* makes the DB unreadable with
sqlite 3.6 which is still widely deployed. Notably if I boot back into
Ubuntu Lucid Lynx
2010/9/19 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com:
2) Contrary to what is stated in the merge request for the event_view
changes the event_view VIEW is *not* regenerated on each startup.
Actually they do, create_db() is executed every time at startup and it
has a DROP VIEW.
--
2010/9/19 Siegfried Gevatter rai...@ubuntu.com:
Actually they do, create_db() is executed every time at startup and it
has a DROP VIEW.
Err, scratch that.
--
WAL and event_view changes requires schema upgrade
https://bugs.launchpad.net/bugs/642772
You received this bug notification because you
I found the following statement in http://www.sqlite.org/wal.html under
Backwards Compatibility
One can explicitly change out of WAL mode using a pragma such as this:
PRAGMA journal_mode=DELETE;
Deliberately changing out of WAL mode changes the database file format
version numbers back to 1 so
4 matches
Mail list logo
