Exchange getChangeCount wrong in transactions
Bug #986465 reported by
Peter Beaman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Akiban Persistit |
New
|
Medium
|
Peter Beaman |
Bug Description
This is a "thought bug" - we haven't yet verified the behavior, but the design appears wrong.
A Tree has a "change count" that gets bumped every time a value is inserted or deleted. This probably doesn't work correctly with MVCC. And since the ConcurrentModif
This is an issue primarily for OE since server doesn't use the functionality.
visibility: | private → public |
To post a comment you must log in.
What's the expected use case? It seems that Accumulators are similar and are already transactional.