DISTINCT key causing internal exception on 2.6.4.b10

Type: BugVersion: 2.6.4Priority: NormalStatus: FixedReplies: 4
#1

I observed that on new ObjectDb v.2.6.4.b10 query below causes internal exception

SELECT DISTINCT $1 FROM Pa3DictionaryItem $2 JOIN $2.values $1 WHERE ($2.namespace == 'com.anritsu.pa3.ttcn3' AND $2.key == 'TliEvent' AND $1 != '')

Query above also worked fine on ObjectDb version 2.6.1.b06

Harman Ltd.
#2

More details are needed.

First, the query in your post is invalid since a closing " is missing at the end of the query. Please check the query.

Second, if there is an internal exception at the minimum the stack trace of that internal exception and the full error message should be posted.

Finally, if you can follow these posting instructions and provide a simple test case that demonstrates the issue it could be very helpful.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#3

First, query is valid since it's worked on prev ObjectDb releases, the problems not in '', just remove DISTINCT and you will see no problems with this query

Second, I have attached

a) Screenshot for used ObjectDb version

b) Original database for reproduce this issue from your side. Have a nice playing 8-)

Harman Ltd.
#4

Thank you very much for this report, and sorry for questioning the validity of your query (the '' suffix looked like a single double quote character " with no closing).

This regression was caused by an incomplete repair of another issue in build 2.6.4_09.

Version 2.6.5 should work well.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#5

Confirming, fixed in 2.6.5 release! Bug may be closed.

Harman Ltd.

Post Reply

To post a reply and/or subscribe to update notifications - please login