[JDO-672] Test case failure: SQLException in ParenthesesMarkOperatorPrecedence

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: JDO 3 (3.0)
• Fix Version/s: JDO 3.1-rc1
• Component/s: tck
• Assignee: Andy Jefferson
• Reporter: Michael Bouschen
• Created: 19/Jan/11 19:31
• Updated: 12/Jun/15 12:53
• Resolved: 29/Jan/11 12:16

Description

The failing test is in jdoql.conf: class org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence method runTestParenthesesMarkOperatorPrecedence08.
The test results in an exception thrown by the derby SQL compiler:

java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER' are not supported. Types must be comparable. String types must also have matching collation. If collation does not match, a possible solution is to cast operands to force them to the default collation (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1')

The derby versions 10.6.1.0 and 10.7.1.1 run into this exception. But it does NOT happen with derby version 10.4.2.0, which we are using in the maven1 environment.

Here is the the JDOQL query:
SELECT FROM org.apache.jdo.tck.pc.mylib.PCPoint EXCLUDE SUBCLASSES WHERE (x == 2) == true
and here is the generated SQL:
SELECT 'org.apache.jdo.tck.pc.mylib.PCPoint' AS NUCLEUS_TYPE,A0.ID,A0.X,A0.Y
FROM APPLICATIONIDENTITY0.PCPOINT A0 WHERE A0.X = 2 = 1

So the question is: what does SQL define when comparing an integer and a boolean?
The expression "A0.X = 2" evaluates to a boolean which is then compared to the integer 1.