** Changed in: unity-2d
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/602211
Title:
Monitoring Create/Move/Copy Files events
Status in
** Changed in: unity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/602211
Title:
Monitoring Create/Move/Copy Files events
Status
** Changed in: unity-lens-files (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/602211
Title:
Monitoring Create/Move/Copy Files events
** Changed in: unity-2d
Status: New = Triaged
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/602211
Title:
Monitoring Create/Move/Copy Files events
Status in Unity:
** Branch linked: lp:ubuntu/zeitgeist
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/602211
Title:
Monitoring Create/Move/Copy Files events
Status in Unity:
Triaged
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/602211
Title:
Monitoring Create/Move/Copy Files events
So I added a logic to handle MOVE_EVENTS here
https://code.launchpad.net/~zeitgeist/zeitgeist/move-event/+merge/53132
please review
** Changed in: zeitgeist
Status: Confirmed = In Progress
** Branch linked: lp:~zeitgeist/zeitgeist/move-event
--
You received this bug notification because
** Changed in: zeitgeist
Milestone: 0.7.0 = None
--
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Unity: Triaged
On 15 November 2010 21:08, Siegfried Gevatter rai...@ubuntu.com wrote:
2010/11/15 Michal Hruby michal@gmail.com:
I still didn't understand why would the current_uri be part of event,
isn't it by definition a property of the subject? That way you don't
need to update dozens of events, just
Agreed I think I am overthinking it a bit. I am pretty ok with this solution
but we shouldn't jump dive into it unless we are pretty comfortable all of
us. What will break is also an issue for me..
On Tue, Nov 16, 2010 at 11:06 PM, Mikkel Kamstrup Erlandsen
mikkel.kamst...@gmail.com wrote:
On
I think it easy for clients to determine subjects that have been deleted
by calling exists on the uri. Of course we can detect delete events from
nautilus too and thusly change the current_uri for it.
But again to the solution for solving moved files. The solution proposed by
Mikkel (modified by
+1 to Mikkel on using it for deletes too, having two different systems
doesn't make sense.
Also, I'd keep uri and current_uri as separate things (current_uri
being a new parameter in event, that's why it's a nice array...), else
this is going to be a real mess.
--
Monitoring Create/Move/Copy
I still didn't understand why would the current_uri be part of event,
isn't it by definition a property of the subject? That way you don't
need to update dozens of events, just one subject entry...
--
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received
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
All of these clever remapping schemes scare me a bit to be honest.
They all seem to imply a non-negligible impact on our query time, and
a considerable amount of logic.
A simpler and more performant scheme, which requires an API break (!),
is to simply add an extra field on our Subject structure
** Changed in: unity
Status: New = Triaged
** Changed in: unity
Importance: Undecided = Low
** Also affects: unity-place-files
Importance: Undecided
Status: New
** Changed in: unity-place-files
Importance: Undecided = Low
** Changed in: unity-place-files
Status:
foo.txt gets renamed to nice.txt, then to stuff.txt, there's a new foo.txt,
stuff.txt gets renamed to omg!!.
renames
---
old_uri | new_uri | timestamp
foo.txtomg!! 1234
nice.txt omg!! 2500
stuff.txt omg!! 5000
events with
I dont understand the soltuion tbh
However looking at your table i got an idea
Scenario:
* foo.txt gets renamed to nice.txt
* nice.txt gets renamed to stuff.txt
* create new foo.txt,
* stuff.txt gets renamed to omg!!
uri
=
id | value
---
1 | foo.txt
2 | nice.txt
3 | stuff.txt
OK I think we can just add 1 column that links to the new uri in the uri
table so it becomes
id | uri | new_id
so i i have a uri xxx
1 | xxx | 1
if its moved or renamed from xxx to yyy we have
1 | xxx | 2
2 | yyy | 2
OR we can do it the other way round by having the new column reference
to
2010/11/9 Seif Lotfy 602...@bugs.launchpad.net:
OK I think we can just add 1 column that links to the new uri in the uri
table so it becomes
Keep in mind that the same URI can be reused for different things,
though. I may rename foo.txt to bar.txt and create a new foo.txt.
--
Monitoring
** Changed in: zeitgeist
Assignee: (unassigned) = Seif Lotfy (seif)
** Changed in: zeitgeist-datahub
Status: Incomplete = New
--
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zeitgeist
I am aware of that issue and am brainstorming to solve it.
for that we will need to have 2 more columns
lets try your example:
event with foo.txt
uri_id | value | new_uri_id | old_uri_id |
-
1 | foo.txt | -1 | -1
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
** Also affects: unity
Importance: Undecided
Status: New
--
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
OK what would happen if we use our uri table as our lookup table and add
the above table as the uri_tracking_table
Another though would be actually to have the normal uri_table and a new
update_uri_table
where we link and id to its new id
so moving foo to bar will give us
** Description changed:
- I was thinking on how tracker monitors new files to index. Turns out they
monitor directories using inotify. Recurse XDG dirs and single iterate $HOME
- Does this make sense to us?
+ An issue we are facing at the moment is that ppl lose track of there files in
a
That is why i proposed solution 2 which in my opinion covers everything
:)
On Sun, Nov 7, 2010 at 2:36 PM, Siegfried Gevatter
rai...@ubuntu.comwrote:
1) Modify the uris in the uris table
-1, events are immutable by definition, they aren't supposed to change
--
Monitoring Create/Move/Copy
awesome :)
On Sun, Nov 7, 2010 at 9:15 PM, S. Sickert s.sick...@gmail.com wrote:
I agree that 95% of the user never use the commandline, so that's not a
big problem.
AFAIK renaming in nautilus is just moving the file.
--
Monitoring Create/Move/Copy Files events
28 matches
Mail list logo
