New db_layout:

uri_id (p) | lookup_id (f) | new_uri_id | old_uri_id |
1 | 1234 | 2 | -1
2 | 1235 | -1 | 1 
3 | 1234 | -1 | -1

Lookup Table: id <-> uri:

lookup_id (p) | value 
1234 | foo.txt
1235 | bar.txt

(p) - primary key
(f) - foreign key

This solves the previous mentioned problems, but breaks compatibility with the 
old db schema.
It don't know, how SQLite actually optimise the old schema, but I think a good 
DBMS should do this already.

Monitoring Create/Move/Copy Files events
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.

Status in Unity: New
Status in Zeitgeist Framework: Confirmed
Status in Zeitgeist Datahub: New

Bug description:
An issue we are facing at the moment is that ppl lose track of there files in a 
timeline if the file was moved around or renamed. I would propose using 
taskview or patch nautilus to actually grab those events and either:
1) Modify the uris in the uris table
2) Create a new table with    | new_id | old_uri_id | event | to map uris to 
their actual ids and the event that allowed the change, this would allow us to 
track a history of renaming or moving a file. It will look a bit like the 

9 | 9 | 48124  # CREATE EVENT
12 | 9 | 48126 # MOVE EVENT

In other words the last row means uri 12 was moved from uri 9 with event 48126


3) Create a changable_uri table that is a map of the uri table. it gets updated 
upon moved and rename.
We then add new resulttype that allow you to ask for either pureSubject or 
adaptedSubject. depending on which one is chosen we then use the according 
table in the join of the find_events_query :)

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to