88 words

Issue #266 - A bug in the JDOQL processor in recent versions of ObjectDB

BugVersion: 2.6.4Priority: NormalStatus: FixedReplies: 2
#1
2016-01-25 07:50

There seems to be a bug in the JDOQL processor in recent versions of ObjectDB. I've uploaded a "laptop" example to demonstrate the problem. The query in Test1.main should return "ThinkMachine MAX SX 20", but it returns incorrect "Media Central Media 555". Earlier versions (at least up to 2.5.4) correctly return "ThinkMachine MAX SX 20".

Regards.

kk8yukawa
kk8yukawa's picture
Joined on 2011-02-13
User Post #1
#2
2016-01-25 16:06

Thank you for this report. Please try build 2.6.5_06 that should fix the bug.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support
support's picture
Joined on 2010-05-03
User Post #2,394
#3
2016-01-25 23:26

This has fixed the bug and the similar ones I spotted.

Thanks.

kk8yukawa
kk8yukawa's picture
Joined on 2011-02-13
User Post #2

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.
Attachments:
Maximum file size: 32 MB
Cancel