Looks like the bug is not fully fixed: I was browsing an OrderedContainer's _data attribute in historical mode which triggered a bug in a different object because the OrderedContainer's _order had keys that were present in _data's latest version but not in the historical version I was looking at.
zodbbrowser should not affect other requests in any way!
Looks like the bug is not fully fixed: I was browsing an OrderedContainer's _data attribute in historical mode which triggered a bug in a different object because the OrderedContainer's _order had keys that were present in _data's latest version but not in the historical version I was looking at.
zodbbrowser should not affect other requests in any way!