Public bug reported:
It just happened:
PythonArgs: ['/usr/bin/zeitgeist-datahub']
Traceback:
Traceback (most recent call last):
File "/usr/bin/zeitgeist-datahub", line 110, in _update_db_async
self._insert_events(self._sources_queue[0].get_name(), events)
File "/usr/bin/zeitgeist-data
Oh yeah, of course. Indeed, good work Siegfried.
While reading the last few comments one possible fix came into my mind:
Let's maintain a (temporary) helper table called '_fix_cache' with (table_name
VARCHAR, id INTEGER) and create a 'BEFORE DELETE' trigger on each cached table
(interpretation, m
I don't have any clever solution off the top of my head - I just want
to give Siegfried some props for the cool detective work! Nice job!
Now. To thinking.
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Un
Review: Needs Fixing
I haven't properly reviewed this yet - but this caught my eye:
48 + CONSTRAINT actor_fk FOREIGN KEY(origin)
49 + REFERENCES uri(id) ON DELETE CASCADE,
I think it should be CONSTRAINT origin_fk instead, right?
--
https://code.launchpad.net/~zeitgeist/zeitgeist/dbsch
4 matches
Mail list logo