127 words

Issue #268 - Query execution creates a wrong result

BugVersion: 2.6.5Priority: CriticalStatus: FixedReplies: 1
2016-02-25 12:40


we analysed an unexpected behavior and find out that the result of an Query are wrong.

We prepared an Example that shows the BUG. (see attachment)

The Example executes two Queries. The first returns an expected result (one Entity). The second Query is the first Query with an additional WHERE condition. But than we get another (wrong) result.


We used Version 2.6.5 and the BUG is fixed with Version 2.6.6.  But we report the BUG, because a wrong Query result is very very Critical and we didn't found a notice in the ReleaseNotes for this BUG.

btc_es's picture
Joined on 2014-10-20
User Post #99
2016-02-26 15:25

Thank you for this report. Build 2.6.6 includes several query processing bug fixes, including issue #266, which is mentioned in the change log and may be related to this report.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support's picture
Joined on 2010-05-03
User Post #2,443

Post Reply

Please read carefully the posting instructions - before posting to the ObjectDB website.

  • You may have to disable pop up blocking in order to use the toolbar (e.g. in Chrome).
  • Use ctrl + right click to open the browser context menu in the editing area (e.g. for using a browser spell checker).
  • To insert formatted lines (e.g. Java code, stack trace) - select a style in the toolbar and then insert the text in the new created block.
  • Avoid overflow of published source code examples by breaking long lines.
  • You may mark in paragraph code words (e.g. class names) with the code style (can be applied by ctrl + D).
  • Long stack traces (> 50 lines) and complex source examples (> 100 lines) should be posted as attachments.
Maximum file size: 32 MB