[Zeitgeist] [Bug 642772] Re: WAL and event_view changes requires schema upgrade

2010-10-01 Thread Seif Lotfy
@thekorn what is your take on this issue. Since WAL stuff has been taken
out we still need your take on 2) so we can close this bug

** Changed in: zeitgeist
   Status: New = Confirmed

-- 
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: Confirmed

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


[Zeitgeist] [Bug 642772] Re: WAL and event_view changes requires schema upgrade

2010-09-22 Thread Seif Lotfy
I reverted the WAL changes so this way the part one of the bug is not
either fixed or invalid

-- 
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


[Zeitgeist] [Bug 642772] Re: WAL and event_view changes requires schema upgrade

2010-09-19 Thread Markus Korn
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.



___
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] Re: WAL and event_view changes requires schema upgrade

2010-09-19 Thread Seif Lotfy
Hmmm I can't really figure out a good fix for this:
1) We revert the WAL change :(
2) We create a translation script that copies the DB content 1-to-1 in a new
db file in case something below sqlite 3.7 is used

On Sun, Sep 19, 2010 at 3:48 PM, Markus Korn thek...@gmx.de wrote:

 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 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


[Zeitgeist] [Bug 642772] Re: WAL and event_view changes requires schema upgrade

2010-09-19 Thread Launchpad Bug Tracker
** Branch linked: lp:~zeitgeist/zeitgeist/fix-642772

-- 
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] Re: WAL and event_view changes requires schema upgrade

2010-09-19 Thread Seif Lotfy
from what I understand people with who dual boot are confronted with this
issue right?

On Sun, Sep 19, 2010 at 4:22 PM, Launchpad Bug Tracker 
642...@bugs.launchpad.net wrote:

 ** Branch linked: lp:~zeitgeist/zeitgeist/fix-642772

 --
 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