So my take on this would be to check every table upon startup for validity.
This requires however that we know what current scheme the db is on how how the
structure would look like.
This means we need to store the table structures and compare them on startup.
We will be confronted with two scenar
** Changed in: zeitgeist (Ubuntu)
Status: Incomplete => Invalid
--
zeitgeist-datahub crash when opening activity journal
https://bugs.launchpad.net/bugs/626056
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framewor
Again to sum it up. My new suggestion is:
* change the event table to include current_subject_uri
* add a logic that handles MOVE/COPY/RENAME events
* listen to MOVE/COPY/RENAME events from outside sources such as nautilus
(by patching, ssickert has a patch)
--
Monitoring Create/Move/Copy Files e
3 matches
Mail list logo