[#3207] Need to update History when moving an object between shares
Summary Need to update History when moving an object between shares
Queue Horde Base
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners Jan Schneider <jan (at) horde (dot) org>
Requester Chuck Hagenbuch <chuck (at) horde (dot) org>
Created 12/28/2005 (975 days ago)
Due
Updated 08/20/2008 (9 days ago)
Assigned 05/31/2008 (90 days ago)
Resolved 08/20/2008 (9 days ago)
Attachments
Milestone
Patch No

History
08/20/2008 CVS Commit Comment #10 Reply to this comment
08/20/2008 Jan Schneider Comment #9
State ⇒ Resolved
Taken from Karsten Fourmont
Taken from Horde DevelopersHorde Developers
Assigned to Jan Schneider
Reply to this comment
Implemented in CVS for all groupware applications. Turba already 
logged that correctly.
08/20/2008 CVS Commit Comment #8 Reply to this comment
08/20/2008 CVS Commit Comment #7 Reply to this comment
08/20/2008 CVS Commit Comment #6 Reply to this comment
05/31/2008 Chuck Hagenbuch Comment #5
State ⇒ Assigned
Assigned to Horde DevelopersHorde Developers
Reply to this comment
From #6785:
"We need to add a pair of delete/add transactions to the history when 
moving objects between shares."
11/24/2007 Chuck Hagenbuch Comment #4
State ⇒ Stalled
Reply to this comment
Stalling for now. Karsten, please re-open or resolve as appropriate.
10/28/2007 Chuck Hagenbuch Comment #3
Taken from Horde DevelopersHorde Developers
State ⇒ Feedback
Reply to this comment
Karsten, is this not actually true, now that we have actual syncing 
experience? Or does it still need to be done?
05/26/2006 Chuck Hagenbuch Comment #2
Assigned to Karsten Fourmont
Reply to this comment
Making sure this is on Karsten's radar as well.
12/28/2005 Chuck Hagenbuch Comment #1
State ⇒ Assigned
Assigned to Horde DevelopersHorde Developers
Queue ⇒ Horde Base
Summary ⇒ Need to update History when moving an object between shares
Priority ⇒ 1. Low
Type ⇒ Bug
Reply to this comment
(do we want a seperate queue for "multiple app" tickets? or one for syncing?)

When moving an object (task, event, etc.) to a new share, we need to:

1. Remove the old history for the object since the history object_uid 
includes the share name for most apps.

2. Re-add with the new correct object_uid.

3. Update the "modify" timestamp, since moving to a new share may 
cause the object to newly appear for some users. It might also cause 
it to disappear for others, but I'm not sure yet how to deal with that.