Destroying renamed items throws an exception
The problem is that renaming preserves the revision's dataid (old revision has some dataid as new revision with the change name metadata), while destroying a revision destroys it related data too.
Say revision a and b have the same dataid, when a first gets destroyed the related data is destroyed. When trying to destroy revision b, an exception is raised.
The solution can be either
1) copy the data when renaming, resulting in a different dataid (like when changing meta only)
2) implement reference counting for data store, instead of destroying related data when destroying a revision