[Zeitgeist] [Merge] lp:~zeitgeist/zeitgeist/pragma-settings into lp:zeitgeist
The proposal to merge lp:~zeitgeist/zeitgeist/pragma-settings into lp:zeitgeist has been updated. Status: Needs review = Merged -- https://code.launchpad.net/~zeitgeist/zeitgeist/pragma-settings/+merge/35833 Your team Zeitgeist Framework Team is subscribed to branch lp:~zeitgeist/zeitgeist/pragma-settings. ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.1
Hello Zeitgeist Framework Team, On 2010-09-19 08:54z (2 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.3
Hello Zeitgeist Framework Team, On 2010-09-19 08:54z (2 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.3 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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 642686] [NEW] Add subj_uri_id and subj_origin_id columns to event_view
Public bug reported: If we add subj_uri_id and subj_origin_id columns to the event_view we could make the prefix searches about 10% faster. Combined with the upcoming optimization of the GLOB statement it will be possible to reduce the avg. time for this kind of queries from ~0.20s to ~0.12s. As always I've added a script where you can test the proposed change to event_view yourself. *** 551 entries starting with 'http://aa' SELECT DISTINCT id FROM event_view WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri IN (SELECT value FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.206047s SELECT DISTINCT id FROM event_view_new WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri_id IN (SELECT id FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.179763s ** Affects: zeitgeist Importance: Wishlist Status: New -- Add subj_uri_id and subj_origin_id columns to event_view https://bugs.launchpad.net/bugs/642686 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: If we add subj_uri_id and subj_origin_id columns to the event_view we could make the prefix searches about 10% faster. Combined with the upcoming optimization of the GLOB statement it will be possible to reduce the avg. time for this kind of queries from ~0.20s to ~0.12s. As always I've added a script where you can test the proposed change to event_view yourself. *** 551 entries starting with 'http://aa' SELECT DISTINCT id FROM event_view WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri IN (SELECT value FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.206047s SELECT DISTINCT id FROM event_view_new WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri_id IN (SELECT id FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.179763s ___ 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 642686] Re: Add subj_uri_id and subj_origin_id columns to event_view
** Attachment added: test_new_event_view.py https://bugs.edge.launchpad.net/bugs/642686/+attachment/1607450/+files/test_new_event_view.py -- Add subj_uri_id and subj_origin_id columns to event_view https://bugs.launchpad.net/bugs/642686 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: If we add subj_uri_id and subj_origin_id columns to the event_view we could make the prefix searches about 10% faster. Combined with the upcoming optimization of the GLOB statement it will be possible to reduce the avg. time for this kind of queries from ~0.20s to ~0.12s. As always I've added a script where you can test the proposed change to event_view yourself. *** 551 entries starting with 'http://aa' SELECT DISTINCT id FROM event_view WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri IN (SELECT value FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.206047s SELECT DISTINCT id FROM event_view_new WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri_id IN (SELECT id FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.179763s ___ 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 642686] Re: Add subj_uri_id and subj_origin_id columns to event_view
** Changed in: zeitgeist Importance: Undecided = Wishlist ** Changed in: zeitgeist Assignee: (unassigned) = Markus Korn (thekorn) ** Changed in: zeitgeist Assignee: Markus Korn (thekorn) = (unassigned) -- Add subj_uri_id and subj_origin_id columns to event_view https://bugs.launchpad.net/bugs/642686 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: If we add subj_uri_id and subj_origin_id columns to the event_view we could make the prefix searches about 10% faster. Combined with the upcoming optimization of the GLOB statement it will be possible to reduce the avg. time for this kind of queries from ~0.20s to ~0.12s. As always I've added a script where you can test the proposed change to event_view yourself. *** 551 entries starting with 'http://aa' SELECT DISTINCT id FROM event_view WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri IN (SELECT value FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.206047s SELECT DISTINCT id FROM event_view_new WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri_id IN (SELECT id FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.179763s ___ 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 642686] Re: Add subj_uri_id and subj_origin_id columns to event_view
** Changed in: zeitgeist Assignee: (unassigned) = Markus Korn (thekorn) ** Changed in: zeitgeist Status: New = In Progress -- Add subj_uri_id and subj_origin_id columns to event_view https://bugs.launchpad.net/bugs/642686 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: If we add subj_uri_id and subj_origin_id columns to the event_view we could make the prefix searches about 10% faster. Combined with the upcoming optimization of the GLOB statement it will be possible to reduce the avg. time for this kind of queries from ~0.20s to ~0.12s. As always I've added a script where you can test the proposed change to event_view yourself. *** 551 entries starting with 'http://aa' SELECT DISTINCT id FROM event_view WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri IN (SELECT value FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.206047s SELECT DISTINCT id FROM event_view_new WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri_id IN (SELECT id FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.179763s ___ 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] [Merge] lp:~thekorn/zeitgeist/fix-642686-eventview-add-origin-and-uri-id into lp:zeitgeist
Markus Korn has proposed merging lp:~thekorn/zeitgeist/fix-642686-eventview-add-origin-and-uri-id into lp:zeitgeist. Requested reviews: Zeitgeist Framework Team (zeitgeist) Related bugs: #642686 Add subj_uri_id and subj_origin_id columns to event_view https://bugs.launchpad.net/bugs/642686 Added 'subj_uri_id' and 'subj_origin_id' columns to event_view (LP: #642686) Note: We don't need to raise the version of our db scheme, as this event_view is regenerated on every startup anyway. -- https://code.launchpad.net/~thekorn/zeitgeist/fix-642686-eventview-add-origin-and-uri-id/+merge/35952 Your team Zeitgeist Framework Team is requested to review the proposed merge of lp:~thekorn/zeitgeist/fix-642686-eventview-add-origin-and-uri-id into lp:zeitgeist. === modified file '_zeitgeist/engine/sql.py' --- _zeitgeist/engine/sql.py 2010-09-18 15:09:08 + +++ _zeitgeist/engine/sql.py 2010-09-19 10:49:40 + @@ -365,10 +365,14 @@ AS payload, (SELECT value FROM uri WHERE uri.id=event.subj_id) AS subj_uri, +(SELECT id FROM uri WHERE uri.id=event.subj_id) + AS subj_uri_id, event.subj_interpretation, event.subj_manifestation, (SELECT value FROM uri WHERE uri.id=event.subj_origin) AS subj_origin, +(SELECT id FROM uri WHERE uri.id=event.subj_origin) + AS subj_origin_id, event.subj_mimetype, (SELECT value FROM text WHERE text.id = event.subj_text) AS subj_text, @@ -484,22 +488,14 @@ def add_text_condition(self, column, value, like=False, negation=False, cache=None): if like: - # thekorn: unfortunatly the data in event_view is a bit inconsistent - # e.g.: - # subj_uri and subj_origin are presented as string-values - # actor and subj_mimetype are ids - # (LP: #580601) + assert column in (subj_uri, subj_origin, actor, subj_mimetype), \ +prefix search on the %r column is not supported by zeitgeist if column in (subj_uri, subj_origin): -value_type = value - elif column in (actor, subj_mimetype): -value_type = id +view_column = %s_id %column else: -raise AssertionError(We don't know how to handle this type of data) - # thekorn: this is a first (unoptimized version) - # see http://www.sqlite.org/optoverview.html '4.0 The LIKE optimization' - # for how this will look in the future - sql = %s %sIN (SELECT %s FROM %s WHERE value GLOB ?) \ - %(column, self.NOT if negation else , value_type, TABLE_MAP.get(column, column)) +view_column = column + sql = %s %sIN (SELECT id FROM %s WHERE value GLOB ?) \ + %(view_column, self.NOT if negation else , TABLE_MAP.get(column, column)) value += * else: sql = %s %s= ? %(column, ! if negation else ) === modified file 'test/sql-test.py' --- test/sql-test.py 2010-05-15 08:45:08 + +++ test/sql-test.py 2010-09-19 10:49:40 + @@ -91,12 +91,12 @@ where = WhereClause(WhereClause.AND) where.add_text_condition(subj_uri, bar, like=True) self.assertEquals(where.sql.replace(?, %s) % tuple(where.arguments), - (subj_uri IN (SELECT value FROM uri WHERE value GLOB bar*))) + (subj_uri_id IN (SELECT id FROM uri WHERE value GLOB bar*))) where = WhereClause(WhereClause.AND) where.add_text_condition(subj_origin, bar, like=True) self.assertEquals(where.sql.replace(?, %s) % tuple(where.arguments), - (subj_origin IN (SELECT value FROM uri WHERE value GLOB bar*))) + (subj_origin_id IN (SELECT id FROM uri WHERE value GLOB bar*))) where = WhereClause(WhereClause.AND) where.add_text_condition(actor, bar, like=True, negation=True) ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.1
Hello Zeitgeist Framework Team, On 2010-09-19 11:09z (31 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.3
Hello Zeitgeist Framework Team, On 2010-09-19 11:09z (31 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.3 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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 642686] Re: Add subj_uri_id and subj_origin_id columns to event_view
** Branch linked: lp:zeitgeist -- Add subj_uri_id and subj_origin_id columns to event_view https://bugs.launchpad.net/bugs/642686 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: If we add subj_uri_id and subj_origin_id columns to the event_view we could make the prefix searches about 10% faster. Combined with the upcoming optimization of the GLOB statement it will be possible to reduce the avg. time for this kind of queries from ~0.20s to ~0.12s. As always I've added a script where you can test the proposed change to event_view yourself. *** 551 entries starting with 'http://aa' SELECT DISTINCT id FROM event_view WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri IN (SELECT value FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.206047s SELECT DISTINCT id FROM event_view_new WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri_id IN (SELECT id FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.179763s ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.1
Hello Zeitgeist Framework Team, On 2010-09-19 11:48z (just requested), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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 642686] Re: Add subj_uri_id and subj_origin_id columns to event_view
** Changed in: zeitgeist Status: In Progress = Fix Committed -- Add subj_uri_id and subj_origin_id columns to event_view https://bugs.launchpad.net/bugs/642686 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Fix Committed Bug description: If we add subj_uri_id and subj_origin_id columns to the event_view we could make the prefix searches about 10% faster. Combined with the upcoming optimization of the GLOB statement it will be possible to reduce the avg. time for this kind of queries from ~0.20s to ~0.12s. As always I've added a script where you can test the proposed change to event_view yourself. *** 551 entries starting with 'http://aa' SELECT DISTINCT id FROM event_view WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri IN (SELECT value FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.206047s SELECT DISTINCT id FROM event_view_new WHERE(timestamp = ? AND timestamp = ? AND ((subj_uri_id IN (SELECT id FROM uri WHERE value GLOB ? ORDER BY timestamp DESC [u'0', u'9223372036854775807', u'http://aa*'] --- get len(ids)=551 using pure sql in 0.179763s ___ 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] [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 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. -- 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
[Zeitgeist] [Bug 642803] [NEW] Today's updates to lp:zeitgeist broke event_view
Public bug reported: As stateted by Mikkel in bug 642772 the event_view is broken for `old` databases Traceback: DBusException: org.freedesktop.DBus.Python.sqlite3.OperationalError: Traceback (most recent call last): File /usr/lib/pymodules/python2.6/dbus/service.py, line 702, in _message_cb retval = candidate_method(self, *args, **keywords) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/remote.py, line 197, in FindEventIds num_events, result_type) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/main.py, line 392, in find_eventids return self._find_events(0, *args) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/main.py, line 375, in _find_events result = self._cursor.execute(sql, where.arguments).fetchall() File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/sql.py, line 59, in execute return super(UnicodeCursor, self).execute(statement, parameters) OperationalError: no such column: subj_uri_id ** Affects: zeitgeist Importance: Critical Assignee: Markus Korn (thekorn) Status: In Progress ** Changed in: zeitgeist Assignee: (unassigned) = Markus Korn (thekorn) ** Changed in: zeitgeist Status: New = In Progress ** Changed in: zeitgeist Importance: Undecided = Critical -- Today's updates to lp:zeitgeist broke event_view https://bugs.launchpad.net/bugs/642803 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: As stateted by Mikkel in bug 642772 the event_view is broken for `old` databases Traceback: DBusException: org.freedesktop.DBus.Python.sqlite3.OperationalError: Traceback (most recent call last): File /usr/lib/pymodules/python2.6/dbus/service.py, line 702, in _message_cb retval = candidate_method(self, *args, **keywords) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/remote.py, line 197, in FindEventIds num_events, result_type) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/main.py, line 392, in find_eventids return self._find_events(0, *args) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/main.py, line 375, in _find_events result = self._cursor.execute(sql, where.arguments).fetchall() File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/sql.py, line 59, in execute return super(UnicodeCursor, self).execute(statement, parameters) OperationalError: no such column: subj_uri_id ___ 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
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
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
Re: [Zeitgeist] [Bug 642772] [NEW] WAL and event_view changes requires schema upgrade
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 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] Translation template import - zeitgeist in Zeitgeist Framework 0.5
Hello Zeitgeist Framework Team, On 2010-09-19 14:26z (1 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.5 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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 642803] Re: Today's updates to lp:zeitgeist broke event_view
** Branch linked: lp:zeitgeist -- Today's updates to lp:zeitgeist broke event_view https://bugs.launchpad.net/bugs/642803 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: As stateted by Mikkel in bug 642772 the event_view is broken for `old` databases Traceback: DBusException: org.freedesktop.DBus.Python.sqlite3.OperationalError: Traceback (most recent call last): File /usr/lib/pymodules/python2.6/dbus/service.py, line 702, in _message_cb retval = candidate_method(self, *args, **keywords) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/remote.py, line 197, in FindEventIds num_events, result_type) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/main.py, line 392, in find_eventids return self._find_events(0, *args) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/main.py, line 375, in _find_events result = self._cursor.execute(sql, where.arguments).fetchall() File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/sql.py, line 59, in execute return super(UnicodeCursor, self).execute(statement, parameters) OperationalError: no such column: subj_uri_id ___ 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 rai...@ubuntu.comwrote: 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 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
** 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
[Zeitgeist] [Bug 642803] Re: Today's updates to lp:zeitgeist broke event_view
** Changed in: zeitgeist Status: In Progress = Fix Committed -- Today's updates to lp:zeitgeist broke event_view https://bugs.launchpad.net/bugs/642803 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Fix Committed Bug description: As stateted by Mikkel in bug 642772 the event_view is broken for `old` databases Traceback: DBusException: org.freedesktop.DBus.Python.sqlite3.OperationalError: Traceback (most recent call last): File /usr/lib/pymodules/python2.6/dbus/service.py, line 702, in _message_cb retval = candidate_method(self, *args, **keywords) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/remote.py, line 197, in FindEventIds num_events, result_type) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/main.py, line 392, in find_eventids return self._find_events(0, *args) File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/main.py, line 375, in _find_events result = self._cursor.execute(sql, where.arguments).fetchall() File /media/devel/zeitgeist/trunk/zeitgeist/../_zeitgeist/engine/sql.py, line 59, in execute return super(UnicodeCursor, self).execute(statement, parameters) OperationalError: no such column: subj_uri_id ___ 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
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
[Zeitgeist] [Bug 642898] Re: Upgrading database scheme is broken for newly created databases
There are two possible solutions for this issue: 1.) check if we are operating on an empty database 2.) change our upgrade function in a way that if a upgrade script is not found for X - Z it tries to run X - Y - Z For 1.) there are two possible ways: 1.a.) check if file already exists before sqlite3.connect() to this file 1.b.) change _get_schema_version() to return -1 if SQLITE_MASTER is empty I vote for 1.a.) as a fix for this bug, and work on 2.) for the future. -- Upgrading database scheme is broken for newly created databases https://bugs.launchpad.net/bugs/642898 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: Todays newly created database version 2 broke the upgrade path, we have no upgrade script for 0 (which means 'no version entry found') to 2. This happens because no-existing databases do not have such table. $ ZEITGEIST_DATABASE_PATH=/tmp/dfgdsfsddf ./zeitgeist-daemon :( DEBUG:root:Checking for another running instance... DEBUG:root:No running instances found. INFO:zeitgeist.sql:Using database: /tmp/dfgdsfsddf DEBUG:zeitgeist.sql:Schema 'core' not found: no such table: schema_version INFO:zeitgeist.sql:Upgrading database 'core' from version 0 to 2. This may take a while CRITICAL:zeitgeist.sql:Failed to upgrade database 'core' from version 0 to 2: No module named core_0_2 We have to check if we are operating on a new database. (Side note: we need tests for upgrades) ___ 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 642898] Re: Upgrading database scheme is broken for newly created databases
+1 for 1.a) ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.1
Hello Zeitgeist Framework Team, On 2010-09-20 05:49z (2 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.3
Hello Zeitgeist Framework Team, On 2010-09-20 05:49z (2 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.3 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ 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] Translation template import - zeitgeist in Zeitgeist Framework 0.5
Hello Zeitgeist Framework Team, On 2010-09-20 05:49z (2 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.5 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
