[
https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980526#action_12980526
]
Michelle Caisse commented on JDO-647:
-------------------------------------
Checked in update for api version. Currently there are three errors x 2
identity types:
In query configuration:
1)
testAVG(org.apache.jdo.tck.query.result.AggregateResult)junit.framework.AssertionFailedError:
Assertion A14.6.9-6 (AggregateResult) failed:
Wrong query result:
query: SELECT AVG(personid) FROM org.apache.jdo.tck.pc.company.Person
expected: java.lang.Double of size 1
3.0
got: java.lang.Long of size 1
3
2)
testAvg(org.apache.jdo.tck.query.result.ResultExpressions)junit.framework.AssertionFailedError:
Assertion A14.6.9-5 (ResultExpressions) failed:
Wrong query result:
query: SELECT AVG(personid) FROM org.apache.jdo.tck.pc.company.Employee
expected: java.lang.Double of size 1
3.0
got: java.lang.Long of size 1
3
In jdoql configuration:
1)
testPositive(org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence)javax.jdo.JDOException:
Exception thrown when executing query
at
org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:541)
at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:230)
at
org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence.runTestParenthesesMarkOperatorPrecedence08(ParenthesesMarkOperatorPrecedence.java:332)
at
org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence.testPositive(ParenthesesMarkOperatorPrecedence.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:272)
at
org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108)
at
org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148)
at
org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123)
NestedThrowablesStackTrace:
java.sql.SQLSyntaxErrorException: 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')
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement40.<init>(Unknown
Source)
at org.apache.derby.jdbc.Driver40.newEmbedPreparedStatement(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown
Source)
at
com.mchange.v2.c3p0.impl.NewProxyConnection.prepareStatement(NewProxyConnection.java:241)
at
org.datanucleus.store.rdbms.SQLController.getStatementForQuery(SQLController.java:311)
at
org.datanucleus.store.rdbms.query.RDBMSQueryUtils.getPreparedStatementForQuery(RDBMSQueryUtils.java:192)
at
org.datanucleus.store.rdbms.query.JDOQLQuery.performExecute(JDOQLQuery.java:602)
at org.datanucleus.store.query.Query.executeQuery(Query.java:1693)
at org.datanucleus.store.query.Query.executeWithArray(Query.java:1528)
at org.datanucleus.store.query.Query.execute(Query.java:1501)
at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:221)
> Run TCK using Maven2 for consistency
> ------------------------------------
>
> Key: JDO-647
> URL: https://issues.apache.org/jira/browse/JDO-647
> Project: JDO
> Issue Type: Improvement
> Components: tck
> Affects Versions: JDO 3
> Reporter: Andy Jefferson
> Assignee: Michelle Caisse
> Fix For: JDO 3 maintenance release 1
>
> Attachments: api_pom.diff, exectck.zip, exectck.zip,
> JDO-647-pom-properties.zip, pom.xml, pom.xml
>
>
> Since api2 now builds using Maven2 it makes a heck of a lot of sense to
> build/run the TCK using that too. It also means that the DataNucleus M1 repo
> (which only exists for use of this TCK) can be deleted. Please consider
> upgrading to Maven2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
