> 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.txt omg!! 1234 nice.txt omg!! 2500 stuff.txt omg!! 5000
events with timestamp < 1234 use "foo.txt" and find "omg!!" in the table, same for the others. the new "foo.txt" has timestamp > 1234 and isn't in renames; it wasn't renamed.
> Finally foo.txt is renamed to why? and > omg!! gets back to foo.txt
renames --------------- old_uri | new_uri | timestamp nice.txt foo.txt 2500 stuff.txt foo.txt 5000 foo.txt omg!! 6000 omg!! foo.txt 7000
an event with timestamp 2200 has nice.txt which is mapped to foo.txt, events pointing to omg!! older than 7000 are mapped to foo.txt
> 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.txt omg!! 1234
nice.txt omg!! 2500
stuff.txt omg!! 5000
events with timestamp < 1234 use "foo.txt" and find "omg!!"
in the table, same for the others. the new "foo.txt" has timestamp > 1234
and isn't in renames; it wasn't renamed.
> Finally foo.txt is renamed to why? and
> omg!! gets back to foo.txt
renames
---------------
old_uri | new_uri | timestamp
nice.txt foo.txt 2500
stuff.txt foo.txt 5000
foo.txt omg!! 6000
omg!! foo.txt 7000
an event with timestamp 2200 has nice.txt which is mapped to
foo.txt, events pointing to omg!! older than 7000 are mapped to foo.txt