Re: Query test failure with newer derby version (was Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time)
Hi, this is 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. Regards Michael Hi Craig, [...] (2) query test: The failing test is in jdoql.conf: class org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence method runTestParenthesesMarkOperatorPrecedence08. The test runs a JDOQL query with PCPoint as candidate class and (x == 2) == true as filter. It 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. Good catch. Would you have time to file a JIRA with Derby? First I want to take a look at the generated SQL before filing a JIRA. I'll keep you posted. Regards Michael [...] -- *Michael Bouschen* *Prokurist* akquinet t...@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Url: www.akquinet.de http://www.akquinet.de akquinet t...@spree GmbH, Berlin Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680
Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time
Hi, Attendees: Michael Bouschen, Michelle Caisse, Craig Russell Agenda: 1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647 Only two tests are now failing: signature test and a query test. The signature test might be reading the wrong signature file, since there have been a few changes to the signature since 3.0. I looked at the test failures: (1) signature test: The current pom.xml still refers the 3.0 version of jdo-api. The test succeeds after switching the dependency to 3.1-SNAPSHOT. Please note the dependency needs to be changed in exectck and tck! (2) query test: The failing test is in jdoql.conf: class org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence method runTestParenthesesMarkOperatorPrecedence08. The test runs a JDOQL query with PCPoint as candidate class and (x == 2) == true as filter. It 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. Regards Michael Maven now has a process for publishing Apache artifacts. We should look into what is needed to use the staging and publishing repositories. 2. Other issues https://issues.apache.org/jira/browse/JDO-643 should add the tck as an affected component. We should also add test cases for average of more of the types that we support, including BigDecimal and BigInteger. https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO page needs an update. Action Items from weeks past: Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! -- *Michael Bouschen* *Prokurist* akquinet t...@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Url: www.akquinet.de http://www.akquinet.de akquinet t...@spree GmbH, Berlin Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680 -- *Michael Bouschen* *Prokurist* akquinet t...@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Url: www.akquinet.de http://www.akquinet.de akquinet t...@spree GmbH, Berlin Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680
Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time
Hi Michael, On Jan 8, 2011, at 2:33 AM, Michael Bouschen wrote: Hi, Attendees: Michael Bouschen, Michelle Caisse, Craig Russell Agenda: 1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647 Only two tests are now failing: signature test and a query test. The signature test might be reading the wrong signature file, since there have been a few changes to the signature since 3.0. I looked at the test failures: (1) signature test: The current pom.xml still refers the 3.0 version of jdo-api. The test succeeds after switching the dependency to 3.1-SNAPSHOT. Please note the dependency needs to be changed in exectck and tck! (2) query test: The failing test is in jdoql.conf: class org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence method runTestParenthesesMarkOperatorPrecedence08. The test runs a JDOQL query with PCPoint as candidate class and (x == 2) == true as filter. It 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. Good catch. Would you have time to file a JIRA with Derby? Thanks, Craig Regards Michael Maven now has a process for publishing Apache artifacts. We should look into what is needed to use the staging and publishing repositories. 2. Other issues https://issues.apache.org/jira/browse/JDO-643 should add the tck as an affected component. We should also add test cases for average of more of the types that we support, including BigDecimal and BigInteger. https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO page needs an update. Action Items from weeks past: Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! -- *Michael Bouschen* *Prokurist* akquinet t...@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Url: www.akquinet.de http://www.akquinet.de akquinet t...@spree GmbH, Berlin Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680 -- *Michael Bouschen* *Prokurist* akquinet t...@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Url: www.akquinet.de http://www.akquinet.de akquinet t...@spree GmbH, Berlin Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680 Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
Query test failure with newer derby version (was Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time)
Hi Craig, [...] (2) query test: The failing test is in jdoql.conf: class org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence method runTestParenthesesMarkOperatorPrecedence08. The test runs a JDOQL query with PCPoint as candidate class and (x == 2) == true as filter. It 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. Good catch. Would you have time to file a JIRA with Derby? First I want to take a look at the generated SQL before filing a JIRA. I'll keep you posted. Regards Michael [...] -- *Michael Bouschen* *Prokurist* akquinet t...@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Url: www.akquinet.de http://www.akquinet.de akquinet t...@spree GmbH, Berlin Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680
