[Zeitgeist] [Bug 660307] Re: zeitgeist fails to run if its database structure is not complete

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

[Zeitgeist] [Bug 626056] Re: zeitgeist-datahub crash when opening activity journal

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

[Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events

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