[Zeitgeist] [Bug 642772] [NEW] WAL and event_view changes requires schema upgrade
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 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. ** Affects: zeitgeist Importance: Undecided Status: New -- 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. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 642772] [NEW] WAL and event_view changes requires schema upgrade
2010/9/19 Mikkel Kamstrup Erlandsen : > 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. -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer 363DEAE3 -- 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. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 642772] [NEW] WAL and event_view changes requires schema upgrade
2010/9/19 Siegfried Gevatter : > 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 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. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 642772] [NEW] WAL and event_view changes requires schema upgrade
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 that older versions of SQLite can once again access the database file. I am uploading a test fix for this... Please tell me what you think lp:~zeitgeist/zeitgeist/fix-642772 On Sun, Sep 19, 2010 at 4:05 PM, Siegfried Gevatter wrote: > 2010/9/19 Siegfried Gevatter : > > 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 are subscribed to The > Zeitgeist Project. > > 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. > > > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 642772] [NEW] WAL and event_view changes requires schema upgrade
scratch that On Sun, Sep 19, 2010 at 4:22 PM, Seif Lotfy wrote: > 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 that older versions of SQLite can once again > access the database file. > > I am uploading a test fix for this... Please tell me what you think > > lp:~zeitgeist/zeitgeist/fix-642772 > > On Sun, Sep 19, 2010 at 4:05 PM, Siegfried Gevatter wrote: > >> 2010/9/19 Siegfried Gevatter : >> > 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 are subscribed to The >> Zeitgeist Project. >> >> 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. >> >> >> > > > -- > This is me doing some advertisement for my blog http://seilo.geekyogre.com > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
