** Description changed:
MOVE EVENTS
PRESENTATION
By definition, Zeitgeist's events are immutable, and the subject meta-data
they contain is a snapshot of how a given resource was back when the event
happened.
To be useful, some
** Description changed:
+ MOVE EVENTS
+
- RainCT seiflotfy: the query updating current_uri on MOVE_EVENT should only
change stuff with timestampmove_event_timestamp
- seiflotfy RainCT, true
- seiflotfy good catch
- RainCT seiflotfy: there's also
I prefer the first solution :)
--
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/778140
Title:
Time warp problem in MOVE_EVENT handling
Status in Zeitgeist Framework:
We have 2 options here:
1) not inserting a move event before another move event in time
2) Extract the history of the subject and rebuild and change the DB according
to the subject_current_uri
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is
** Branch linked: lp: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/778140
Title:
Time warp problem in MOVE_EVENT handling
Status in Zeitgeist Framework:
5 matches
Mail list logo