Bug 44548

GemStone/S

6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.x, 6.2, 6.1.6, 6.1.5, 6.1.x, 6.0.x, 5.0

Multiple set-valued comparison predicates conjoined with & produce inconsistent results

Due to the design of the query code, multiple predicates that are conjoined with &, that query on the same set-valued collection path, and which use a comparison rather than equality type operator, may produce inconsistent results.

Note that queries that can be restructured by optimization to remove the &, or reduce the predicates to one for the collection path, will not have this problem.

Workaround

We recommend avoiding set-valued indexes in general.  Single-predicate queries, or queries that use =, ~=, ==, and ~~ are not affected by this case.


Last updated: 12/18/15