Bug 36892

GemStone/S 64 Bit

2.2.5.4, 2.2.5.3, 2.2.5.2, 2.2.5.1, 2.2.5, 2.2.x, 2.2, 2.1.4, 2.1.x, 2.1, 2.0.4, 2.0.3, 2.0.x

All

2.3

Create/remove indexes with uncommitted objects may result in errors

If indexes are created on uncommitted collections containing
uncommitted objects, queries on these collections will create
results that include OOPs for the objects.  If the results are
saved, but the collection or any objects in the collection are
removed without committing or the commit fails, this may result in
incorrect answeres or object does not exist errors.

Workaround

Ensure that queries on indexed collections only operate on committed
collections, and that no objects have been added to the collection
since the last commit in this session.


Last updated: 7/3/07