zeitgeist team mailing list archive

[Markus Korn <thekorn@xxxxxx>]

Hi Mikkel,
I'm sorry, number two on your list is definitely my bad. I did not know that this "DROP VIEW [...]" line has no effect, and I also did not test my changes on an already existing database. My changes are indeed not working as I expect them to work.
I'll work on fixing the issue in bug 642803.

Can't say anything to number one on your list, because I was not
involved into the process of deciding about using different options, but
I raised the question about using our db versioning mechanisms here.

Markus

-- 
WAL and event_view changes requires schema upgrade
https://bugs.launchpad.net/bugs/642772
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.

Status in Zeitgeist Framework: New

Bug description:
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 Zeitgeist will no longer work as lucid only ships sqlite 3.6.

 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. That is one of the whole points of doing schema versioning. This change makes Zeitgeist trunk unable to return any results if run on an older db. Strangely enough it doesn't raise any errors...

Guys - if you are making low level changes to our DB structure like both of these changes are, please make sure you understand all the ramifications before merging.