Grokbase › Groups › Cayenne › dev › October 2010
FAQ
Hi Mike (mrg)!

Wonder why we are getting a bunch of Hudson H2 errors? Is this a different H2 version compared to what you've tested against?

Cheers,
Andrus

On Sep 28, 2010, at 4:19 PM, Apache Hudson Server wrote:

See <https://hudson.apache.org/hudson/job/Cayenne-trunk/./cayenneTestConnection=h2,jdk=JDK%201.5%20(latest),label=Ubuntu/372/changes>

Changes:

[mgentry] Updated the H2 Adapter to support auto-generating primary keys through H2's AUTO_INCREMENT option.

------------------------------------------
[...truncated 26528 lines...]
testSetContext(org.apache.cayenne.CayenneDataObjectInContextTest)
testFetchByAttribute(org.apache.cayenne.CayenneDataObjectInContextTest)
testUniquing(org.apache.cayenne.CayenneDataObjectInContextTest)
testSnapshotVersion1(org.apache.cayenne.CayenneDataObjectInContextTest)
testSnapshotVersion2(org.apache.cayenne.CayenneDataObjectInContextTest)
testSnapshotVersion3(org.apache.cayenne.CayenneDataObjectInContextTest)
testObjectsCommittedManualOID(org.apache.cayenne.CayenneDataObjectInContextTest)
testGeneratedJoinInFlattenedRelationship(org.apache.cayenne.access.IdentityColumnsTest)
testCompoundPKWithGeneratedColumn(org.apache.cayenne.access.IdentityColumnsTest)
testDbEntityQualifier(org.apache.cayenne.access.trans.SelectTranslatorTest)
testSave(org.apache.cayenne.access.InheritanceTest)
test(org.apache.cayenne.query.StatementFetchSizeTest)
testPerformPaginatedQuery(org.apache.cayenne.access.DataContextTest)
testCurrentSnapshot1(org.apache.cayenne.access.DataContextTest)
testCurrentSnapshot2(org.apache.cayenne.access.DataContextTest)
testCurrentSnapshot3(org.apache.cayenne.access.DataContextTest)
testCurrentSnapshotWithToOneFault(org.apache.cayenne.access.DataContextTest)
testCharFetch(org.apache.cayenne.access.DataContextTest)
testCharInQualifier(org.apache.cayenne.access.DataContextTest)
testMultiObjRelFetch(org.apache.cayenne.access.DataContextTest)
testMultiDbRelFetch(org.apache.cayenne.access.DataContextTest)
testSelectDate(org.apache.cayenne.access.DataContextTest)
testCaseInsensitiveOrdering(org.apache.cayenne.access.DataContextTest)
testPerformSelectQuery1(org.apache.cayenne.access.DataContextTest)
testPerformSelectQuery2(org.apache.cayenne.access.DataContextTest)
testPerformNonSelectingQuery(org.apache.cayenne.access.DataContextTest)
testPerformNonSelectingQueryCounts1(org.apache.cayenne.access.DataContextTest)
testPerformNonSelectingQueryCounts2(org.apache.cayenne.access.DataContextTest)
testPerformPaginatedQuery1(org.apache.cayenne.access.DataContextTest)
testPerformPaginatedQueryBigPage(org.apache.cayenne.access.DataContextTest)
testPerformDataRowQuery(org.apache.cayenne.access.DataContextTest)
testCommitChangesRO1(org.apache.cayenne.access.DataContextTest)
testCommitChangesRO2(org.apache.cayenne.access.DataContextTest)
testCommitChangesRO3(org.apache.cayenne.access.DataContextTest)
testCommitChangesRO4(org.apache.cayenne.access.DataContextTest)
testPerformIteratedQuery1(org.apache.cayenne.access.DataContextTest)
testPerformIteratedQuery2(org.apache.cayenne.access.DataContextTest)
testHasChangesPhantom(org.apache.cayenne.access.DataContextTest)
testHasChangesRealModify(org.apache.cayenne.access.DataContextTest)
testInvalidateObjects(org.apache.cayenne.access.DataContextTest)
testBeforeHollowDeleteShouldChangeStateToCommited(org.apache.cayenne.access.DataContextTest)
testSelectSelectCommitRefresh(org.apache.cayenne.access.DataContextSharedCacheEmpiricTest)
testSelectSelectCommitRefreshReverse(org.apache.cayenne.access.DataContextSharedCacheEmpiricTest)
testSelectUpdateSelectCommitRefresh(org.apache.cayenne.access.DataContextSharedCacheEmpiricTest)
testGeneratePkForDbEntity(org.apache.cayenne.dba.PkGeneratorTest)
testSerializeNew(org.apache.cayenne.access.DataContextSerializationTest)
testSerializeCommitted(org.apache.cayenne.access.DataContextSerializationTest)
testSerializeResolver(org.apache.cayenne.access.DataContextSerializationTest)
testSerializeChannel(org.apache.cayenne.access.DataContextSerializationTest)
testSerializeNestedChannel(org.apache.cayenne.access.DataContextSerializationTest)
testSerializeWithSharedCache(org.apache.cayenne.access.DataContextSerializationTest)
testSerializeWithLocalCache(org.apache.cayenne.access.DataContextSerializationTest)
testSerializeModified(org.apache.cayenne.access.DataContextSerializationTest)
testLocalObjectSynchronize(org.apache.cayenne.NestedCayenneContextTest)
testLocalObjectsNoOverride(org.apache.cayenne.NestedCayenneContextTest)
testSelect(org.apache.cayenne.NestedCayenneContextTest)
testPrefetchingToOne(org.apache.cayenne.NestedCayenneContextTest)
testPrefetchingToMany(org.apache.cayenne.NestedCayenneContextTest)
testDeleteNew(org.apache.cayenne.NestedCayenneContextTest)
testNullifyToOne(org.apache.cayenne.NestedCayenneContextTest)
testCommitChangesToParent(org.apache.cayenne.NestedCayenneContextTest)
testCommitChangesToParentDeleted(org.apache.cayenne.NestedCayenneContextTest)
testCommitChanges(org.apache.cayenne.NestedCayenneContextTest)
testAddRemove(org.apache.cayenne.NestedCayenneContextTest)
testChangeRel(org.apache.cayenne.NestedCayenneContextTest)
testCAY1183(org.apache.cayenne.NestedCayenneContextTest)
testIterator(org.apache.cayenne.access.SimpleIdIncrementalFaultListDataRowsTest)
testGet1(org.apache.cayenne.access.SimpleIdIncrementalFaultListDataRowsTest)
testIndexOf1(org.apache.cayenne.access.SimpleIdIncrementalFaultListDataRowsTest)
testIndexOf2(org.apache.cayenne.access.SimpleIdIncrementalFaultListDataRowsTest)
testLastIndexOf1(org.apache.cayenne.access.SimpleIdIncrementalFaultListDataRowsTest)
testLastIndexOf2(org.apache.cayenne.access.SimpleIdIncrementalFaultListDataRowsTest)
testCompareToNull(org.apache.cayenne.access.DataContextEJBQLIsNullTest)
testCompareToNull2(org.apache.cayenne.access.DataContextEJBQLIsNullTest)
testCompareToNull3(org.apache.cayenne.access.DataContextEJBQLIsNullTest)
testIsNull(org.apache.cayenne.access.DataContextEJBQLIsNullTest)
testIsNotNull(org.apache.cayenne.access.DataContextEJBQLIsNullTest)
testToOneIsNull(org.apache.cayenne.access.DataContextEJBQLIsNullTest)
testToOneIsNotNull(org.apache.cayenne.access.DataContextEJBQLIsNullTest)
testFetchLimit(org.apache.cayenne.access.DataContextSQLTemplateTest)
testFetchOffset(org.apache.cayenne.access.DataContextSQLTemplateTest)
testPageSize(org.apache.cayenne.access.DataContextSQLTemplateTest)
testSQLResultSetMappingScalar(org.apache.cayenne.access.DataContextSQLTemplateTest)
testSQLResultSetMappingMixed(org.apache.cayenne.access.DataContextSQLTemplateTest)
testSQLResultSetMappingScalarArray(org.apache.cayenne.access.DataContextSQLTemplateTest)
testColumnNamesCapitalization(org.apache.cayenne.access.DataContextSQLTemplateTest)
testFetchDataRows(org.apache.cayenne.access.DataContextSQLTemplateTest)
testFetchObjects(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindObjectEqualShort(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindObjectNotEqualShort(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindObjectEqualFull(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindObjectEqualFullNonArray(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindObjectEqualNull(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindObjectNotEqualFull(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindObjectEqualCompound(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindObjectNotEqualCompound(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindObjectNotEqualNull(org.apache.cayenne.access.DataContextSQLTemplateTest)
testBindEqualNull(org.apache.cayenne.access.DataContextSQLTemplateTest)
testFetchOffsetFetchLimit(org.apache.cayenne.access.DataContextSQLTemplateTest)
testIteratedQuery(org.apache.cayenne.access.DataContextSQLTemplateTest)
testQueryWithLineBreakAfterMacro(org.apache.cayenne.access.DataContextSQLTemplateTest)
testManyToMany(org.apache.cayenne.access.FlattenedPrefetchTest)
testMultiPrefetch(org.apache.cayenne.access.FlattenedPrefetchTest)
testJointManyToMany(org.apache.cayenne.access.FlattenedPrefetchTest)
testJointMultiPrefetch(org.apache.cayenne.access.FlattenedPrefetchTest)
testOrderByDefault(org.apache.cayenne.access.DataContextEJBQLOrderByTest)
testOrderByAsc(org.apache.cayenne.access.DataContextEJBQLOrderByTest)
testOrderByDesc(org.apache.cayenne.access.DataContextEJBQLOrderByTest)
testOrderByQualified(org.apache.cayenne.access.DataContextEJBQLOrderByTest)
testOrderByMultiple(org.apache.cayenne.access.DataContextEJBQLOrderByTest)
testOrderByPath(org.apache.cayenne.access.DataContextEJBQLOrderByTest)
testCollectionMemberOfThetaJoin(org.apache.cayenne.access.DataContextEJBQLFlattenedRelationshipsTest)
testCommitDecorated(org.apache.cayenne.access.DataContextDecoratedStackTest)
testGetParentDataDomain(org.apache.cayenne.access.DataContextDecoratedStackTest)
testLocalCacheStaysLocal(org.apache.cayenne.access.NestedDataContextLocalCacheTest)
testParentUpdatedId(org.apache.cayenne.access.NestedDataContextParentEventsTest)
testUpdateQualifier(org.apache.cayenne.access.DataContextEJBQLUpdateTest)
testUpdateNoQualifierString(org.apache.cayenne.access.DataContextEJBQLUpdateTest)
testUpdateNoQualifierNull(org.apache.cayenne.access.DataContextEJBQLUpdateTest)
testUpdateNoQualifierMultipleItems(org.apache.cayenne.access.DataContextEJBQLUpdateTest)
testUpdateNoQualifierDecimal(org.apache.cayenne.access.DataContextEJBQLUpdateTest)
testUpdateNoQualifierBoolean(org.apache.cayenne.access.DataContextEJBQLUpdateTest)
testUpdateNoQualifierToOne(org.apache.cayenne.access.DataContextEJBQLUpdateTest)
testUpdateNoQualifierToOneCompoundPK(org.apache.cayenne.access.DataContextEJBQLUpdateTest)
testFetchLimit(org.apache.cayenne.query.SelectQueryTest)
testFetchOffset(org.apache.cayenne.query.SelectQueryTest)
testDbEntityRoot(org.apache.cayenne.query.SelectQueryTest)
testFetchLimitWithOffset(org.apache.cayenne.query.SelectQueryTest)
testFetchOffsetWithQualifier(org.apache.cayenne.query.SelectQueryTest)
testFetchLimitWithQualifier(org.apache.cayenne.query.SelectQueryTest)
testSelectAllObjectsRootEntityName(org.apache.cayenne.query.SelectQueryTest)
testSelectAllObjectsRootClass(org.apache.cayenne.query.SelectQueryTest)
testSelectAllObjectsRootObjEntity(org.apache.cayenne.query.SelectQueryTest)
testSelectLikeExactMatch(org.apache.cayenne.query.SelectQueryTest)
testSelectNotLikeSingleWildcardMatch(org.apache.cayenne.query.SelectQueryTest)
testSelectNotLikeIgnoreCaseSingleWildcardMatch(org.apache.cayenne.query.SelectQueryTest)
testSelectLikeCaseSensitive(org.apache.cayenne.query.SelectQueryTest)
testSelectLikeSingleWildcardMatch(org.apache.cayenne.query.SelectQueryTest)
testSelectLikeSingleWildcardMatchAndEscape(org.apache.cayenne.query.SelectQueryTest)
testSelectLikeMultipleWildcardMatch(org.apache.cayenne.query.SelectQueryTest)
testSelectLikeIgnoreCaseObjects1(org.apache.cayenne.query.SelectQueryTest)
testSelectLikeIgnoreCaseObjects2(org.apache.cayenne.query.SelectQueryTest)
testSelectLikeIgnoreCaseClob(org.apache.cayenne.query.SelectQueryTest)
testSelectIn(org.apache.cayenne.query.SelectQueryTest)
testSelectParameterizedIn(org.apache.cayenne.query.SelectQueryTest)
testSelectParameterizedEmptyIn(org.apache.cayenne.query.SelectQueryTest)
testSelectParameterizedEmptyNotIn(org.apache.cayenne.query.SelectQueryTest)
testSelectEmptyIn(org.apache.cayenne.query.SelectQueryTest)
testSelectEmptyNotIn(org.apache.cayenne.query.SelectQueryTest)
testSelectBooleanTrue(org.apache.cayenne.query.SelectQueryTest)
testSelectBooleanNotTrueOr(org.apache.cayenne.query.SelectQueryTest)
testSelectBooleanFalse(org.apache.cayenne.query.SelectQueryTest)
testSelectBooleanFalseOr(org.apache.cayenne.query.SelectQueryTest)
testRouteWithPrefetches(org.apache.cayenne.query.SelectQueryTest)
testRouteQueryWithPrefetchesNoReverse(org.apache.cayenne.query.SelectQueryTest)
testRouteQueryWithPrefetchesPrefetchExpressionPath(org.apache.cayenne.query.SelectQueryTest)
testLeftJoinAndPrefetchToMany(org.apache.cayenne.query.SelectQueryTest)
testLeftJoinAndPrefetchToOne(org.apache.cayenne.query.SelectQueryTest)
testRollbackRelationshipModification(org.apache.cayenne.remote.RemoteRollbackTest)
testRollbackDeletedObject(org.apache.cayenne.remote.RemoteRollbackTest)
testRollbackModifiedObject(org.apache.cayenne.remote.RemoteRollbackTest)
testNullify(org.apache.cayenne.remote.RelationshipChangeTest)
testChange(org.apache.cayenne.remote.RelationshipChangeTest)
testAddToMany(org.apache.cayenne.CDOCollectionRelationshipTest)
testAddToManyViaReverse(org.apache.cayenne.CDOCollectionRelationshipTest)
testFlushToParent_Commit(org.apache.cayenne.access.DataContextCommitTest)
testDeepMergeExistingSubclass(org.apache.cayenne.util.DeepMergeOperationInheritanceTest)
testDeepMergeNonExistentSubclass(org.apache.cayenne.util.DeepMergeOperationInheritanceTest)
testReadRelationship(org.apache.cayenne.CDOOneToManyFKTest)
testGeneratedKey(org.apache.cayenne.access.DataContextEntityWithMeaningfulPKTest)
testToManyRelationshipWithMeaningfulPK2(org.apache.cayenne.access.DataContextEntityWithMeaningfulPKTest)
testNotLike(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testIn(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testNotIn(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testOr(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testAnd(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testNot(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testEqual(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testNotEqual(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testLessThan(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testLessThanEqualTo(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testGreaterThan(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testGreaterThanEqualTo(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testLike(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testLikeIgnoreCase(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testNotLikeIgnoreCase(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testBetween(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testNotBetween(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testParameter(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testDbExpression(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testFloatExpression(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testNullExpression(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testTrueExpression(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testFalseExpression(org.apache.cayenne.exp.ParsedExpQualifierCompatTest)
testMultipleOrdering(org.apache.cayenne.access.DataContextOrderingTest)
testMultipleOrderingInSelectClauseCAY_1074(org.apache.cayenne.access.DataContextOrderingTest)
testCommit(org.apache.cayenne.access.UserTransactionTest)
testLocalObjectPeerContextMap(org.apache.cayenne.access.DataContextObjectTrackingTest)
testLocalObjectPeerContextNoOverride(org.apache.cayenne.access.DataContextObjectTrackingTest)
testFetchLimit_DistinctResultIterator(org.apache.cayenne.access.jdbc.SelectActionTest)
testLocalCacheRefreshObjectsRefresh(org.apache.cayenne.access.DataContextQueryCachingTest)
testPeerObjectUpdatedSimpleProperty(org.apache.cayenne.access.NestedDataContextParentPeerEventsTest)
testPeerObjectUpdatedToOneRelationship(org.apache.cayenne.access.NestedDataContextParentPeerEventsTest)
testPeerObjectUpdatedToManyRelationship(org.apache.cayenne.access.NestedDataContextParentPeerEventsTest)

Tests run: 2065, Failures: 3, Errors: 851, Skipped: 0

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.

Please refer to <https://hudson.apache.org/hudson/job/Cayenne-trunk/./cayenneTestConnection=h2,jdk=JDK%201.5%20(latest),label=Ubuntu/ws/trunk/framework/cayenne-jdk1.5-unpublished/target/surefire-reports> for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to <https://hudson.apache.org/hudson/job/Cayenne-trunk/./cayenneTestConnection=h2,jdk=JDK%201.5%20(latest),label=Ubuntu/ws/trunk/framework/cayenne-jdk1.5-unpublished/target/surefire-reports> for the individual test results.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.

Please refer to <https://hudson.apache.org/hudson/job/Cayenne-trunk/./cayenneTestConnection=h2,jdk=JDK%201.5%20(latest),label=Ubuntu/ws/trunk/framework/cayenne-jdk1.5-unpublished/target/surefire-reports> for the individual test results.
at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:629)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 50 seconds
[INFO] Finished at: Tue Sep 28 13:19:26 UTC 2010
[INFO] Final Memory: 73M/431M
[INFO] ------------------------------------------------------------------------
Recording test results

Search Discussions

  • Michael Gentry at Oct 4, 2010 at 7:39 pm ⇧
    Hi Andrus,

    I saw that error e-mail, but when I built and ran tests I didn't get
    the errors. Wouldn't the version of H2 to use when running tests be
    specified in the pom.xml and in theory should be the same? Is this
    still happening? I haven't seen any more Hudson failures since then.

    Thanks,

    mrg

    On Mon, Oct 4, 2010 at 3:15 PM, Andrus Adamchik wrote:
    Hi Mike (mrg)!

    Wonder why we are getting a bunch of Hudson H2 errors? Is this a different H2 version compared to what you've tested against?

    Cheers,
    Andrus


    On Sep 28, 2010, at 4:19 PM, Apache Hudson Server wrote:

    [spew deleted]
  • Andrus Adamchik at Oct 4, 2010 at 7:56 pm ⇧
    yeah, I'd think so:

    <dependency>
    <groupId>com.h2database</groupId>
    <artifactId>h2</artifactId>
    <version>1.0.64</version>
    <scope>test</scope>
    </dependency>
    I haven't seen any more Hudson failures since then.
    All my today's commits resulted in the same failures. Build #373.

    Andrus
    On Oct 4, 2010, at 10:38 PM, Michael Gentry wrote:

    Hi Andrus,

    I saw that error e-mail, but when I built and ran tests I didn't get
    the errors. Wouldn't the version of H2 to use when running tests be
    specified in the pom.xml and in theory should be the same? Is this
    still happening? I haven't seen any more Hudson failures since then.

    Thanks,

    mrg

    On Mon, Oct 4, 2010 at 3:15 PM, Andrus Adamchik wrote:
    Hi Mike (mrg)!

    Wonder why we are getting a bunch of Hudson H2 errors? Is this a different H2 version compared to what you've tested against?

    Cheers,
    Andrus


    On Sep 28, 2010, at 4:19 PM, Apache Hudson Server wrote:

    [spew deleted]
  • Andrus Adamchik at Oct 4, 2010 at 8:05 pm ⇧
    Just reproduced the errors locally running like this:

    mvn clean install -DcayenneTestConnection=h2

    Could you doublecheck the property name activating the "h2" profile? It is different between 3.0 and 3.1 branches (above is a 3.1 version per http://cayenne.apache.org/running-unit-tests.html ). The new syntax is due to some stupid Hudson limitations on dots in the property names.

    Andrus
    On Oct 4, 2010, at 10:55 PM, Andrus Adamchik wrote:

    yeah, I'd think so:

    <dependency>
    <groupId>com.h2database</groupId>
    <artifactId>h2</artifactId>
    <version>1.0.64</version>
    <scope>test</scope>
    </dependency>
    I haven't seen any more Hudson failures since then.
    All my today's commits resulted in the same failures. Build #373.

    Andrus
    On Oct 4, 2010, at 10:38 PM, Michael Gentry wrote:

    Hi Andrus,

    I saw that error e-mail, but when I built and ran tests I didn't get
    the errors. Wouldn't the version of H2 to use when running tests be
    specified in the pom.xml and in theory should be the same? Is this
    still happening? I haven't seen any more Hudson failures since then.

    Thanks,

    mrg

    On Mon, Oct 4, 2010 at 3:15 PM, Andrus Adamchik wrote:
    Hi Mike (mrg)!

    Wonder why we are getting a bunch of Hudson H2 errors? Is this a different H2 version compared to what you've tested against?

    Cheers,
    Andrus


    On Sep 28, 2010, at 4:19 PM, Apache Hudson Server wrote:

    [spew deleted]
  • Michael Gentry at Oct 4, 2010 at 8:19 pm ⇧
    Just tried with -DcayenneTestConnection=h2, which I hadn't used before:

    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESSFUL
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 4 minutes 17 seconds
    [INFO] Finished at: Mon Oct 04 16:17:03 EDT 2010
    [INFO] Final Memory: 101M/309M
    [INFO] ------------------------------------------------------------------------

    On Mon, Oct 4, 2010 at 4:04 PM, Andrus Adamchik wrote:
    Just reproduced the errors locally running like this:

    mvn clean install -DcayenneTestConnection=h2

    Could you doublecheck the property name activating the "h2" profile? It is different between 3.0 and 3.1 branches (above is a 3.1 version per http://cayenne.apache.org/running-unit-tests.html ). The new syntax is due to some stupid Hudson limitations on dots in the property names.

    Andrus
    On Oct 4, 2010, at 10:55 PM, Andrus Adamchik wrote:

    yeah, I'd think so:

    <dependency>
    <groupId>com.h2database</groupId>
    <artifactId>h2</artifactId>
    <version>1.0.64</version>
    <scope>test</scope>
    </dependency>
    I haven't seen any more Hudson failures since then.
    All my today's commits resulted in the same failures. Build #373.

    Andrus
    On Oct 4, 2010, at 10:38 PM, Michael Gentry wrote:

    Hi Andrus,

    I saw that error e-mail, but when I built and ran tests I didn't get
    the errors.  Wouldn't the version of H2 to use when running tests be
    specified in the pom.xml and in theory should be the same?  Is this
    still happening?  I haven't seen any more Hudson failures since then.

    Thanks,

    mrg

    On Mon, Oct 4, 2010 at 3:15 PM, Andrus Adamchik wrote:
    Hi Mike (mrg)!

    Wonder why we are getting a bunch of Hudson H2 errors? Is this a different H2 version compared to what you've tested against?

    Cheers,
    Andrus


    On Sep 28, 2010, at 4:19 PM, Apache Hudson Server wrote:

    [spew deleted]
  • Michael Gentry at Oct 4, 2010 at 8:24 pm ⇧
    I hadn't updated since I did the H2 tweak, so I just updated to pick
    up your change and any others. Same story:

    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESSFUL
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 3 minutes 49 seconds
    [INFO] Finished at: Mon Oct 04 16:22:58 EDT 2010
    [INFO] Final Memory: 101M/309M
    [INFO] ------------------------------------------------------------------------


    Not sure what is going on with Hudson at the moment.

    mrg

    On Mon, Oct 4, 2010 at 4:18 PM, Michael Gentry wrote:
    Just tried with -DcayenneTestConnection=h2, which I hadn't used before:

    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESSFUL
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 4 minutes 17 seconds
    [INFO] Finished at: Mon Oct 04 16:17:03 EDT 2010
    [INFO] Final Memory: 101M/309M
    [INFO] ------------------------------------------------------------------------

    On Mon, Oct 4, 2010 at 4:04 PM, Andrus Adamchik wrote:
    Just reproduced the errors locally running like this:

    mvn clean install -DcayenneTestConnection=h2

    Could you doublecheck the property name activating the "h2" profile? It is different between 3.0 and 3.1 branches (above is a 3.1 version per http://cayenne.apache.org/running-unit-tests.html ). The new syntax is due to some stupid Hudson limitations on dots in the property names.

    Andrus
    On Oct 4, 2010, at 10:55 PM, Andrus Adamchik wrote:

    yeah, I'd think so:

    <dependency>
    <groupId>com.h2database</groupId>
    <artifactId>h2</artifactId>
    <version>1.0.64</version>
    <scope>test</scope>
    </dependency>
    I haven't seen any more Hudson failures since then.
    All my today's commits resulted in the same failures. Build #373.

    Andrus
    On Oct 4, 2010, at 10:38 PM, Michael Gentry wrote:

    Hi Andrus,

    I saw that error e-mail, but when I built and ran tests I didn't get
    the errors.  Wouldn't the version of H2 to use when running tests be
    specified in the pom.xml and in theory should be the same?  Is this
    still happening?  I haven't seen any more Hudson failures since then.

    Thanks,

    mrg

    On Mon, Oct 4, 2010 at 3:15 PM, Andrus Adamchik wrote:
    Hi Mike (mrg)!

    Wonder why we are getting a bunch of Hudson H2 errors? Is this a different H2 version compared to what you've tested against?

    Cheers,
    Andrus


    On Sep 28, 2010, at 4:19 PM, Apache Hudson Server wrote:

    [spew deleted]
  • Andrus Adamchik at Oct 5, 2010 at 6:46 am ⇧

    On Oct 4, 2010, at 11:24 PM, Michael Gentry wrote:

    Not sure what is going on with Hudson at the moment.
    It is not just Hudson. It is reproducible on my machine.

    Just tried with -DcayenneTestConnection=h2, which I hadn't used before:
    So let's compare Maven output. At the test phase of the cayenne-jdk1.5-unpublished project it should print H2 adapter and URL:

    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.access.trans.BatchQueryBuilderTest
    Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.1 sec
    Running org.apache.cayenne.unit.di.DICaseSelfTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 sec
    Running org.apache.cayenne.exp.parser.ExpressionEvaluateInMemoryTest
    Oct 5, 2010 9:44:23 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
    INFO: Loading XML bean definitions from resource loaded through InputStream
    Oct 5, 2010 9:44:23 AM org.springframework.core.CollectionFactory <clinit>
    INFO: Commons Collections 3.x available
    Oct 5, 2010 9:44:23 AM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: test connection info: [org.apache.cayenne.conn.DataSourceInfo:
    user name: username
    password: **********
    driver: org.h2.Driver
    db adapter class: org.apache.cayenne.dba.h2.H2Adapter
    url: jdbc:h2:mem:myTestMem;MVCC=TRUE
    min. connections: 1
    max. connections: 1
    ]


    Andrus
  • Michael Gentry at Oct 5, 2010 at 12:51 pm ⇧
    Hi Andrus,

    Mine gives:

    INFO: Invalid connection key 'h2', trying default: internal_embedded_datasource

    And then uses HSQLDB.

    mrg


    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.access.trans.BatchQueryBuilderTest
    Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.427 sec
    Running org.apache.cayenne.unit.di.DICaseSelfTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec
    Running org.apache.cayenne.exp.parser.ExpressionEvaluateInMemoryTest
    Oct 4, 2010 4:20:00 PM
    org.springframework.beans.factory.xml.XmlBeanDefinitionReader
    loadBeanDefinitions
    INFO: Loading XML bean definitions from resource loaded through InputStream
    Oct 4, 2010 4:20:00 PM org.springframework.core.CollectionFactory <clinit>
    INFO: Commons Collections 3.x available
    Oct 4, 2010 4:20:00 PM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: Invalid connection key 'h2', trying default: internal_embedded_datasource
    Oct 4, 2010 4:20:00 PM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: test connection info: [org.apache.cayenne.conn.DataSourceInfo:
    user name: sa
    password: **********
    driver: org.hsqldb.jdbcDriver
    db adapter class: org.apache.cayenne.dba.hsqldb.HSQLDBAdapter
    url: jdbc:hsqldb:mem:aname
    min. connections: 1
    max. connections: 1
    ]

    On Tue, Oct 5, 2010 at 2:46 AM, Andrus Adamchik wrote:
    On Oct 4, 2010, at 11:24 PM, Michael Gentry wrote:

    Not sure what is going on with Hudson at the moment.
    It is not just Hudson. It is reproducible on my machine.

    Just tried with -DcayenneTestConnection=h2, which I hadn't used before:
    So let's compare Maven output. At the test phase of the cayenne-jdk1.5-unpublished project it should print H2 adapter and URL:

    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.access.trans.BatchQueryBuilderTest
    Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.1 sec
    Running org.apache.cayenne.unit.di.DICaseSelfTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 sec
    Running org.apache.cayenne.exp.parser.ExpressionEvaluateInMemoryTest
    Oct 5, 2010 9:44:23 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
    INFO: Loading XML bean definitions from resource loaded through InputStream
    Oct 5, 2010 9:44:23 AM org.springframework.core.CollectionFactory <clinit>
    INFO: Commons Collections 3.x available
    Oct 5, 2010 9:44:23 AM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: test connection info: [org.apache.cayenne.conn.DataSourceInfo:
    user name: username
    password: **********
    driver: org.h2.Driver
    db adapter class: org.apache.cayenne.dba.h2.H2Adapter
    url: jdbc:h2:mem:myTestMem;MVCC=TRUE
    min. connections: 1
    max. connections: 1
    ]


    Andrus

  • Andrus Adamchik at Oct 5, 2010 at 12:56 pm ⇧
    That explains it. You need to configure in-memory H2. E.g. here is mine:

    ~: cat ~/.cayenne/connection.properties |grep h2

    h2.cayenne.adapter = org.apache.cayenne.dba.h2.H2Adapter
    h2.jdbc.username = username
    h2.jdbc.password = password
    h2.jdbc.url = jdbc:h2:mem:myTestMem;MVCC=TRUE
    h2.jdbc.driver = org.h2.Driver

    Andrus
    On Oct 5, 2010, at 3:49 PM, Michael Gentry wrote:

    Hi Andrus,

    Mine gives:

    INFO: Invalid connection key 'h2', trying default: internal_embedded_datasource

    And then uses HSQLDB.

    mrg


    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.access.trans.BatchQueryBuilderTest
    Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.427 sec
    Running org.apache.cayenne.unit.di.DICaseSelfTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec
    Running org.apache.cayenne.exp.parser.ExpressionEvaluateInMemoryTest
    Oct 4, 2010 4:20:00 PM
    org.springframework.beans.factory.xml.XmlBeanDefinitionReader
    loadBeanDefinitions
    INFO: Loading XML bean definitions from resource loaded through InputStream
    Oct 4, 2010 4:20:00 PM org.springframework.core.CollectionFactory <clinit>
    INFO: Commons Collections 3.x available
    Oct 4, 2010 4:20:00 PM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: Invalid connection key 'h2', trying default: internal_embedded_datasource
    Oct 4, 2010 4:20:00 PM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: test connection info: [org.apache.cayenne.conn.DataSourceInfo:
    user name: sa
    password: **********
    driver: org.hsqldb.jdbcDriver
    db adapter class: org.apache.cayenne.dba.hsqldb.HSQLDBAdapter
    url: jdbc:hsqldb:mem:aname
    min. connections: 1
    max. connections: 1
    ]

    On Tue, Oct 5, 2010 at 2:46 AM, Andrus Adamchik wrote:
    On Oct 4, 2010, at 11:24 PM, Michael Gentry wrote:

    Not sure what is going on with Hudson at the moment.
    It is not just Hudson. It is reproducible on my machine.

    Just tried with -DcayenneTestConnection=h2, which I hadn't used before:
    So let's compare Maven output. At the test phase of the cayenne-jdk1.5-unpublished project it should print H2 adapter and URL:

    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.access.trans.BatchQueryBuilderTest
    Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.1 sec
    Running org.apache.cayenne.unit.di.DICaseSelfTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 sec
    Running org.apache.cayenne.exp.parser.ExpressionEvaluateInMemoryTest
    Oct 5, 2010 9:44:23 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
    INFO: Loading XML bean definitions from resource loaded through InputStream
    Oct 5, 2010 9:44:23 AM org.springframework.core.CollectionFactory <clinit>
    INFO: Commons Collections 3.x available
    Oct 5, 2010 9:44:23 AM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: test connection info: [org.apache.cayenne.conn.DataSourceInfo:
    user name: username
    password: **********
    driver: org.h2.Driver
    db adapter class: org.apache.cayenne.dba.h2.H2Adapter
    url: jdbc:h2:mem:myTestMem;MVCC=TRUE
    min. connections: 1
    max. connections: 1
    ]


    Andrus

  • Michael Gentry at Oct 5, 2010 at 1:06 pm ⇧
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] There are test failures.


    Now I have something to look at. :-)

    On Tue, Oct 5, 2010 at 8:55 AM, Andrus Adamchik wrote:
    That explains it. You need to configure in-memory H2. E.g. here is mine:

    ~: cat ~/.cayenne/connection.properties |grep h2

    h2.cayenne.adapter = org.apache.cayenne.dba.h2.H2Adapter
    h2.jdbc.username = username
    h2.jdbc.password = password
    h2.jdbc.url = jdbc:h2:mem:myTestMem;MVCC=TRUE
    h2.jdbc.driver = org.h2.Driver

    Andrus
    On Oct 5, 2010, at 3:49 PM, Michael Gentry wrote:

    Hi Andrus,

    Mine gives:

    INFO: Invalid connection key 'h2', trying default: internal_embedded_datasource

    And then uses HSQLDB.

    mrg


    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.access.trans.BatchQueryBuilderTest
    Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.427 sec
    Running org.apache.cayenne.unit.di.DICaseSelfTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec
    Running org.apache.cayenne.exp.parser.ExpressionEvaluateInMemoryTest
    Oct 4, 2010 4:20:00 PM
    org.springframework.beans.factory.xml.XmlBeanDefinitionReader
    loadBeanDefinitions
    INFO: Loading XML bean definitions from resource loaded through InputStream
    Oct 4, 2010 4:20:00 PM org.springframework.core.CollectionFactory <clinit>
    INFO: Commons Collections 3.x available
    Oct 4, 2010 4:20:00 PM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: Invalid connection key 'h2', trying default: internal_embedded_datasource
    Oct 4, 2010 4:20:00 PM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: test connection info: [org.apache.cayenne.conn.DataSourceInfo:
    user name: sa
    password: **********
    driver: org.hsqldb.jdbcDriver
    db adapter class: org.apache.cayenne.dba.hsqldb.HSQLDBAdapter
    url: jdbc:hsqldb:mem:aname
    min. connections: 1
    max. connections: 1
    ]

    On Tue, Oct 5, 2010 at 2:46 AM, Andrus Adamchik wrote:
    On Oct 4, 2010, at 11:24 PM, Michael Gentry wrote:

    Not sure what is going on with Hudson at the moment.
    It is not just Hudson. It is reproducible on my machine.

    Just tried with -DcayenneTestConnection=h2, which I hadn't used before:
    So let's compare Maven output. At the test phase of the cayenne-jdk1.5-unpublished project it should print H2 adapter and URL:

    -------------------------------------------------------
    T E S T S
    -------------------------------------------------------
    Running org.apache.cayenne.access.trans.BatchQueryBuilderTest
    Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.1 sec
    Running org.apache.cayenne.unit.di.DICaseSelfTest
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 sec
    Running org.apache.cayenne.exp.parser.ExpressionEvaluateInMemoryTest
    Oct 5, 2010 9:44:23 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
    INFO: Loading XML bean definitions from resource loaded through InputStream
    Oct 5, 2010 9:44:23 AM org.springframework.core.CollectionFactory <clinit>
    INFO: Commons Collections 3.x available
    Oct 5, 2010 9:44:23 AM org.apache.cayenne.unit.CayenneResources setConnectionKey
    INFO: test connection info: [org.apache.cayenne.conn.DataSourceInfo:
    user name: username
    password: **********
    driver: org.h2.Driver
    db adapter class: org.apache.cayenne.dba.h2.H2Adapter
    url: jdbc:h2:mem:myTestMem;MVCC=TRUE
    min. connections: 1
    max. connections: 1
    ]


    Andrus

  • Michael Gentry at Oct 5, 2010 at 1:54 pm ⇧
    One issue it is failing with:

    SEVERE: Error generating schema...
    org.h2.jdbc.JdbcSQLException: Attempt to define a second primary key;
    SQL statement:
    CREATE TABLE GENERATED_COLUMN_COMP_KEY (AUTO_PK INTEGER NOT NULL,
    GENERATED_COLUMN INTEGER NOT NULL AUTO_INCREMENT, NAME VARCHAR(100)
    NULL, PROPAGATED_PK INTEGER NOT NULL, PRIMARY KEY (AUTO_PK,
    GENERATED_COLUMN, PROPAGATED_PK)) [90017-64]


    The test map has the following:


    <db-entity name="GENERATED_COLUMN_COMP_KEY">
    <db-attribute name="AUTO_PK" type="INTEGER"
    isPrimaryKey="true" isMandatory="true"/>
    <db-attribute name="GENERATED_COLUMN" type="INTEGER"
    isPrimaryKey="true" isGenerated="true" isMandatory="true"/>
    <db-attribute name="NAME" type="VARCHAR" length="100"/>
    <db-attribute name="PROPAGATED_PK" type="INTEGER"
    isPrimaryKey="true" isMandatory="true"/>
    </db-entity>

    I'm guessing that H2 doesn't allow multiple/compound PKs if one of
    them is autogenerated. Thoughts?

    Thanks,

    mrg
  • Michael Gentry at Oct 5, 2010 at 3:04 pm ⇧
    The following SQL:

    CREATE TABLE GENERATED_COLUMN_COMP_KEY (AUTO_PK INTEGER NOT NULL,
    GENERATED_COLUMN INTEGER NOT NULL AUTO_INCREMENT, NAME VARCHAR(100)
    NULL, PROPAGATED_PK INTEGER NOT NULL, PRIMARY KEY (AUTO_PK,
    GENERATED_COLUMN, PROPAGATED_PK))

    h2-1.0.61: fail
    h2-1.2.128: pass

    We are using 1.0.64 in the pom.xml. Perhaps we should use a newer version?

    mrg
  • Andrus Adamchik at Oct 5, 2010 at 4:17 pm ⇧
    Totally, let's upgrade.
    On Oct 5, 2010, at 6:04 PM, Michael Gentry wrote:

    The following SQL:

    CREATE TABLE GENERATED_COLUMN_COMP_KEY (AUTO_PK INTEGER NOT NULL,
    GENERATED_COLUMN INTEGER NOT NULL AUTO_INCREMENT, NAME VARCHAR(100)
    NULL, PROPAGATED_PK INTEGER NOT NULL, PRIMARY KEY (AUTO_PK,
    GENERATED_COLUMN, PROPAGATED_PK))

    h2-1.0.61: fail
    h2-1.2.128: pass

    We are using 1.0.64 in the pom.xml. Perhaps we should use a newer version?

    mrg
  • Michael Gentry at Oct 5, 2010 at 4:26 pm ⇧
    svn commit -m "Updated h2 from 1.0.64 to 1.2.143" pom.xml

    Not sure if everything will run, but problem won't hurt. :-)

    On Tue, Oct 5, 2010 at 12:16 PM, Andrus Adamchik wrote:
    Totally, let's upgrade.
    On Oct 5, 2010, at 6:04 PM, Michael Gentry wrote:

    The following SQL:

    CREATE TABLE GENERATED_COLUMN_COMP_KEY (AUTO_PK INTEGER NOT NULL,
    GENERATED_COLUMN INTEGER NOT NULL AUTO_INCREMENT, NAME VARCHAR(100)
    NULL, PROPAGATED_PK INTEGER NOT NULL, PRIMARY KEY (AUTO_PK,
    GENERATED_COLUMN, PROPAGATED_PK))

    h2-1.0.61: fail
    h2-1.2.128: pass

    We are using 1.0.64 in the pom.xml.  Perhaps we should use a newer version?

    mrg
  • Michael Gentry at Oct 6, 2010 at 12:17 am ⇧
    Still a few errors being generated. I haven't had a lot of time to
    look into it. One issue is:

    DataContextEJBQLConditionsTest.testCollectionEmpty

    It inserts 3 artists and 3 paintings. 2 paintings off 1 artist, 1
    painting off another artist, and 1 artist with 0 paintings. It then
    uses:

    ejbql = "SELECT a FROM Artist a WHERE a.paintingArray IS EMPTY";

    to create an EJBQLQuery which executes:

    INFO: SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL
    Oct 5, 2010 8:03:38 PM org.apache.cayenne.log.CommonsJdbcEventLogger
    logSelectCount
    INFO: === returned 3 rows. - took 41 ms.

    All 3 artists seem to be returned instead of just the 1 artist without
    a painting. This causes:

    assertEquals(1, objects.size());

    to fail. I'm not sure if this is an H2 issue or something else.
    Obviously it seems to have happened after I updated the adapter to
    support auto increment PKs. :-)

    mrg
  • Andrus Adamchik at Oct 6, 2010 at 7:02 am ⇧

    On Oct 6, 2010, at 3:17 AM, Michael Gentry wrote:

    Obviously it seems to have happened after I updated the adapter to
    support auto increment PKs. :-)
    I suspect the real issue for these remaining failures is actually H2 version upgrade.

    Andrus
  • Michael Gentry at Oct 6, 2010 at 2:22 pm ⇧
    Well, I just manually created the ARTIST and PAINTING table and added
    the 3 records in each using the H2 1.2.143 console. I then did the
    query and it returned only 1 row (the correct one). So something more
    is going on here.

    mrg

    On Wed, Oct 6, 2010 at 3:01 AM, Andrus Adamchik wrote:
    On Oct 6, 2010, at 3:17 AM, Michael Gentry wrote:

    Obviously it seems to have happened after I updated the adapter to
    support auto increment PKs.  :-)
    I suspect the real issue for these remaining failures is actually H2 version upgrade.

    Andrus
  • Michael Gentry at Oct 9, 2010 at 3:24 pm ⇧
    Hi,

    I just did an experiment. Using H2 against a file (/tmp/CayenneTest)
    it worked fine (returned one record). Against an in memory DB it
    failed (returned 3 records). Seems like there is a bug in H2
    somewhere. Thoughts on how we should handle this?

    Thanks,

    mrg

    PS. Here is the SQL:


    CREATE TABLE ARTIST (ARTIST_ID BIGINT NOT NULL, ARTIST_NAME CHAR(254)
    NOT NULL, DATE_OF_BIRTH DATE NULL, PRIMARY KEY (ARTIST_ID));
    CREATE TABLE PAINTING (ARTIST_ID BIGINT NULL, ESTIMATED_PRICE
    DECIMAL(10, 2) NULL, GALLERY_ID INTEGER NULL, PAINTING_DESCRIPTION
    VARCHAR(255) NULL, PAINTING_ID INTEGER NOT NULL, PAINTING_TITLE
    VARCHAR(255) NOT NULL, PRIMARY KEY (PAINTING_ID));

    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33001, 'B');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33002, 'A');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33003, 'D');
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33009, 33001, 'X', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33010, 33001, 'Y', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33011, 33002, 'Z', 5000);

    SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL;
  • Andrus Adamchik at Oct 9, 2010 at 3:30 pm ⇧
    I suggest filing a bug with H2 and downgrading down, until we (hopefully) find a version that is free of that bug but still supports auto-increment. If that doesn't work, we can switch tests to file-based URLs.

    Andrus

    On Oct 9, 2010, at 6:23 PM, Michael Gentry wrote:
    Hi,

    I just did an experiment. Using H2 against a file (/tmp/CayenneTest)
    it worked fine (returned one record). Against an in memory DB it
    failed (returned 3 records). Seems like there is a bug in H2
    somewhere. Thoughts on how we should handle this?

    Thanks,

    mrg

    PS. Here is the SQL:


    CREATE TABLE ARTIST (ARTIST_ID BIGINT NOT NULL, ARTIST_NAME CHAR(254)
    NOT NULL, DATE_OF_BIRTH DATE NULL, PRIMARY KEY (ARTIST_ID));
    CREATE TABLE PAINTING (ARTIST_ID BIGINT NULL, ESTIMATED_PRICE
    DECIMAL(10, 2) NULL, GALLERY_ID INTEGER NULL, PAINTING_DESCRIPTION
    VARCHAR(255) NULL, PAINTING_ID INTEGER NOT NULL, PAINTING_TITLE
    VARCHAR(255) NOT NULL, PRIMARY KEY (PAINTING_ID));

    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33001, 'B');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33002, 'A');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33003, 'D');
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33009, 33001, 'X', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33010, 33001, 'Y', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33011, 33002, 'Z', 5000);

    SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL;
  • Michael Gentry at Oct 9, 2010 at 4:06 pm ⇧
    H2 1.1.119 ran tests successfully locally, so I've committed the POM
    and hopefully Hudson will build cleanly now.

    mrg

    On Sat, Oct 9, 2010 at 11:29 AM, Andrus Adamchik wrote:
    I suggest filing a bug with H2 and downgrading down, until we (hopefully) find a version that is free of that bug but still supports auto-increment. If that doesn't work, we can switch tests to file-based URLs.

    Andrus

    On Oct 9, 2010, at 6:23 PM, Michael Gentry wrote:
    Hi,

    I just did an experiment.  Using H2 against a file (/tmp/CayenneTest)
    it worked fine (returned one record).  Against an in memory DB it
    failed (returned 3 records).  Seems like there is a bug in H2
    somewhere.  Thoughts on how we should handle this?

    Thanks,

    mrg

    PS. Here is the SQL:


    CREATE TABLE ARTIST (ARTIST_ID BIGINT NOT NULL, ARTIST_NAME CHAR(254)
    NOT NULL, DATE_OF_BIRTH DATE NULL, PRIMARY KEY (ARTIST_ID));
    CREATE TABLE PAINTING (ARTIST_ID BIGINT NULL, ESTIMATED_PRICE
    DECIMAL(10, 2) NULL, GALLERY_ID INTEGER NULL, PAINTING_DESCRIPTION
    VARCHAR(255) NULL, PAINTING_ID INTEGER NOT NULL, PAINTING_TITLE
    VARCHAR(255) NOT NULL, PRIMARY KEY (PAINTING_ID));

    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33001, 'B');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33002, 'A');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33003, 'D');
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33009, 33001, 'X', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33010, 33001, 'Y', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33011, 33002, 'Z', 5000);

    SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL;
  • Andrus Adamchik at Oct 9, 2010 at 8:25 pm ⇧
    Awesome. It worked.

    Can we possibly log a Jira about H2 auto increment feature and record it in RELEASE-NOTES? It should help us down the line in documenting 3.1 improvements.

    Andrus

    On Oct 9, 2010, at 7:05 PM, Michael Gentry wrote:

    H2 1.1.119 ran tests successfully locally, so I've committed the POM
    and hopefully Hudson will build cleanly now.

    mrg

    On Sat, Oct 9, 2010 at 11:29 AM, Andrus Adamchik wrote:
    I suggest filing a bug with H2 and downgrading down, until we (hopefully) find a version that is free of that bug but still supports auto-increment. If that doesn't work, we can switch tests to file-based URLs.

    Andrus

    On Oct 9, 2010, at 6:23 PM, Michael Gentry wrote:
    Hi,

    I just did an experiment. Using H2 against a file (/tmp/CayenneTest)
    it worked fine (returned one record). Against an in memory DB it
    failed (returned 3 records). Seems like there is a bug in H2
    somewhere. Thoughts on how we should handle this?

    Thanks,

    mrg

    PS. Here is the SQL:


    CREATE TABLE ARTIST (ARTIST_ID BIGINT NOT NULL, ARTIST_NAME CHAR(254)
    NOT NULL, DATE_OF_BIRTH DATE NULL, PRIMARY KEY (ARTIST_ID));
    CREATE TABLE PAINTING (ARTIST_ID BIGINT NULL, ESTIMATED_PRICE
    DECIMAL(10, 2) NULL, GALLERY_ID INTEGER NULL, PAINTING_DESCRIPTION
    VARCHAR(255) NULL, PAINTING_ID INTEGER NOT NULL, PAINTING_TITLE
    VARCHAR(255) NOT NULL, PRIMARY KEY (PAINTING_ID));

    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33001, 'B');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33002, 'A');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33003, 'D');
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33009, 33001, 'X', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33010, 33001, 'Y', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33011, 33002, 'Z', 5000);

    SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL;
  • Michael Gentry at Oct 9, 2010 at 11:14 pm ⇧
    Sure, I'll take care of that. I also filed a bug for the H2 people.
    Maybe they'll fix it, but at least we are back to building now.

    mrg

    On Sat, Oct 9, 2010 at 4:24 PM, Andrus Adamchik wrote:
    Awesome. It worked.

    Can we possibly log a Jira about H2 auto increment feature and record it in RELEASE-NOTES? It should help us down the line in documenting 3.1 improvements.

    Andrus

    On Oct 9, 2010, at 7:05 PM, Michael Gentry wrote:

    H2 1.1.119 ran tests successfully locally, so I've committed the POM
    and hopefully Hudson will build cleanly now.

    mrg

    On Sat, Oct 9, 2010 at 11:29 AM, Andrus Adamchik wrote:
    I suggest filing a bug with H2 and downgrading down, until we (hopefully) find a version that is free of that bug but still supports auto-increment. If that doesn't work, we can switch tests to file-based URLs.

    Andrus

    On Oct 9, 2010, at 6:23 PM, Michael Gentry wrote:
    Hi,

    I just did an experiment.  Using H2 against a file (/tmp/CayenneTest)
    it worked fine (returned one record).  Against an in memory DB it
    failed (returned 3 records).  Seems like there is a bug in H2
    somewhere.  Thoughts on how we should handle this?

    Thanks,

    mrg

    PS. Here is the SQL:


    CREATE TABLE ARTIST (ARTIST_ID BIGINT NOT NULL, ARTIST_NAME CHAR(254)
    NOT NULL, DATE_OF_BIRTH DATE NULL, PRIMARY KEY (ARTIST_ID));
    CREATE TABLE PAINTING (ARTIST_ID BIGINT NULL, ESTIMATED_PRICE
    DECIMAL(10, 2) NULL, GALLERY_ID INTEGER NULL, PAINTING_DESCRIPTION
    VARCHAR(255) NULL, PAINTING_ID INTEGER NOT NULL, PAINTING_TITLE
    VARCHAR(255) NOT NULL, PRIMARY KEY (PAINTING_ID));

    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33001, 'B');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33002, 'A');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33003, 'D');
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33009, 33001, 'X', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33010, 33001, 'Y', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33011, 33002, 'Z', 5000);

    SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL;
  • Michael Gentry at Oct 21, 2010 at 2:30 pm ⇧
    FWIW, the H2 people fixed the bug for us and 3.1 builds and the tests
    successfully run with with H2 1.2.144.

    mrg

    On Sat, Oct 9, 2010 at 7:13 PM, Michael Gentry wrote:
    Sure, I'll take care of that.  I also filed a bug for the H2 people.
    Maybe they'll fix it, but at least we are back to building now.

    mrg

    On Sat, Oct 9, 2010 at 4:24 PM, Andrus Adamchik wrote:
    Awesome. It worked.

    Can we possibly log a Jira about H2 auto increment feature and record it in RELEASE-NOTES? It should help us down the line in documenting 3.1 improvements.

    Andrus

    On Oct 9, 2010, at 7:05 PM, Michael Gentry wrote:

    H2 1.1.119 ran tests successfully locally, so I've committed the POM
    and hopefully Hudson will build cleanly now.

    mrg

    On Sat, Oct 9, 2010 at 11:29 AM, Andrus Adamchik wrote:
    I suggest filing a bug with H2 and downgrading down, until we (hopefully) find a version that is free of that bug but still supports auto-increment. If that doesn't work, we can switch tests to file-based URLs.

    Andrus

    On Oct 9, 2010, at 6:23 PM, Michael Gentry wrote:
    Hi,

    I just did an experiment.  Using H2 against a file (/tmp/CayenneTest)
    it worked fine (returned one record).  Against an in memory DB it
    failed (returned 3 records).  Seems like there is a bug in H2
    somewhere.  Thoughts on how we should handle this?

    Thanks,

    mrg

    PS. Here is the SQL:


    CREATE TABLE ARTIST (ARTIST_ID BIGINT NOT NULL, ARTIST_NAME CHAR(254)
    NOT NULL, DATE_OF_BIRTH DATE NULL, PRIMARY KEY (ARTIST_ID));
    CREATE TABLE PAINTING (ARTIST_ID BIGINT NULL, ESTIMATED_PRICE
    DECIMAL(10, 2) NULL, GALLERY_ID INTEGER NULL, PAINTING_DESCRIPTION
    VARCHAR(255) NULL, PAINTING_ID INTEGER NOT NULL, PAINTING_TITLE
    VARCHAR(255) NOT NULL, PRIMARY KEY (PAINTING_ID));

    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33001, 'B');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33002, 'A');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33003, 'D');
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33009, 33001, 'X', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33010, 33001, 'Y', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33011, 33002, 'Z', 5000);

    SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL;
  • Andrus Adamchik at Oct 21, 2010 at 2:32 pm ⇧
    Nice!
    On Oct 21, 2010, at 5:29 PM, Michael Gentry wrote:

    FWIW, the H2 people fixed the bug for us and 3.1 builds and the tests
    successfully run with with H2 1.2.144.

    mrg

    On Sat, Oct 9, 2010 at 7:13 PM, Michael Gentry wrote:
    Sure, I'll take care of that. I also filed a bug for the H2 people.
    Maybe they'll fix it, but at least we are back to building now.

    mrg

    On Sat, Oct 9, 2010 at 4:24 PM, Andrus Adamchik wrote:
    Awesome. It worked.

    Can we possibly log a Jira about H2 auto increment feature and record it in RELEASE-NOTES? It should help us down the line in documenting 3.1 improvements.

    Andrus

    On Oct 9, 2010, at 7:05 PM, Michael Gentry wrote:

    H2 1.1.119 ran tests successfully locally, so I've committed the POM
    and hopefully Hudson will build cleanly now.

    mrg

    On Sat, Oct 9, 2010 at 11:29 AM, Andrus Adamchik wrote:
    I suggest filing a bug with H2 and downgrading down, until we (hopefully) find a version that is free of that bug but still supports auto-increment. If that doesn't work, we can switch tests to file-based URLs.

    Andrus

    On Oct 9, 2010, at 6:23 PM, Michael Gentry wrote:
    Hi,

    I just did an experiment. Using H2 against a file (/tmp/CayenneTest)
    it worked fine (returned one record). Against an in memory DB it
    failed (returned 3 records). Seems like there is a bug in H2
    somewhere. Thoughts on how we should handle this?

    Thanks,

    mrg

    PS. Here is the SQL:


    CREATE TABLE ARTIST (ARTIST_ID BIGINT NOT NULL, ARTIST_NAME CHAR(254)
    NOT NULL, DATE_OF_BIRTH DATE NULL, PRIMARY KEY (ARTIST_ID));
    CREATE TABLE PAINTING (ARTIST_ID BIGINT NULL, ESTIMATED_PRICE
    DECIMAL(10, 2) NULL, GALLERY_ID INTEGER NULL, PAINTING_DESCRIPTION
    VARCHAR(255) NULL, PAINTING_ID INTEGER NOT NULL, PAINTING_TITLE
    VARCHAR(255) NOT NULL, PRIMARY KEY (PAINTING_ID));

    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33001, 'B');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33002, 'A');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33003, 'D');
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33009, 33001, 'X', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33010, 33001, 'Y', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33011, 33002, 'Z', 5000);

    SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL;
  • Michael Gentry at Oct 21, 2010 at 2:37 pm ⇧
    Dare we switch? :-)


    On Thu, Oct 21, 2010 at 10:31 AM, Andrus Adamchik
    wrote:
    Nice!
    On Oct 21, 2010, at 5:29 PM, Michael Gentry wrote:

    FWIW, the H2 people fixed the bug for us and 3.1 builds and the tests
    successfully run with with H2 1.2.144.

    mrg

    On Sat, Oct 9, 2010 at 7:13 PM, Michael Gentry wrote:
    Sure, I'll take care of that.  I also filed a bug for the H2 people.
    Maybe they'll fix it, but at least we are back to building now.

    mrg

    On Sat, Oct 9, 2010 at 4:24 PM, Andrus Adamchik wrote:
    Awesome. It worked.

    Can we possibly log a Jira about H2 auto increment feature and record it in RELEASE-NOTES? It should help us down the line in documenting 3.1 improvements.

    Andrus

    On Oct 9, 2010, at 7:05 PM, Michael Gentry wrote:

    H2 1.1.119 ran tests successfully locally, so I've committed the POM
    and hopefully Hudson will build cleanly now.

    mrg

    On Sat, Oct 9, 2010 at 11:29 AM, Andrus Adamchik wrote:
    I suggest filing a bug with H2 and downgrading down, until we (hopefully) find a version that is free of that bug but still supports auto-increment. If that doesn't work, we can switch tests to file-based URLs.

    Andrus

    On Oct 9, 2010, at 6:23 PM, Michael Gentry wrote:
    Hi,

    I just did an experiment.  Using H2 against a file (/tmp/CayenneTest)
    it worked fine (returned one record).  Against an in memory DB it
    failed (returned 3 records).  Seems like there is a bug in H2
    somewhere.  Thoughts on how we should handle this?

    Thanks,

    mrg

    PS. Here is the SQL:


    CREATE TABLE ARTIST (ARTIST_ID BIGINT NOT NULL, ARTIST_NAME CHAR(254)
    NOT NULL, DATE_OF_BIRTH DATE NULL, PRIMARY KEY (ARTIST_ID));
    CREATE TABLE PAINTING (ARTIST_ID BIGINT NULL, ESTIMATED_PRICE
    DECIMAL(10, 2) NULL, GALLERY_ID INTEGER NULL, PAINTING_DESCRIPTION
    VARCHAR(255) NULL, PAINTING_ID INTEGER NOT NULL, PAINTING_TITLE
    VARCHAR(255) NOT NULL, PRIMARY KEY (PAINTING_ID));

    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33001, 'B');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33002, 'A');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33003, 'D');
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33009, 33001, 'X', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33010, 33001, 'Y', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33011, 33002, 'Z', 5000);

    SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL;
  • Andrus Adamchik at Oct 21, 2010 at 3:24 pm ⇧
    Of course.
    On Oct 21, 2010, at 5:36 PM, Michael Gentry wrote:

    Dare we switch? :-)


    On Thu, Oct 21, 2010 at 10:31 AM, Andrus Adamchik
    wrote:
    Nice!
    On Oct 21, 2010, at 5:29 PM, Michael Gentry wrote:

    FWIW, the H2 people fixed the bug for us and 3.1 builds and the tests
    successfully run with with H2 1.2.144.

    mrg

    On Sat, Oct 9, 2010 at 7:13 PM, Michael Gentry wrote:
    Sure, I'll take care of that. I also filed a bug for the H2 people.
    Maybe they'll fix it, but at least we are back to building now.

    mrg

    On Sat, Oct 9, 2010 at 4:24 PM, Andrus Adamchik wrote:
    Awesome. It worked.

    Can we possibly log a Jira about H2 auto increment feature and record it in RELEASE-NOTES? It should help us down the line in documenting 3.1 improvements.

    Andrus

    On Oct 9, 2010, at 7:05 PM, Michael Gentry wrote:

    H2 1.1.119 ran tests successfully locally, so I've committed the POM
    and hopefully Hudson will build cleanly now.

    mrg

    On Sat, Oct 9, 2010 at 11:29 AM, Andrus Adamchik wrote:
    I suggest filing a bug with H2 and downgrading down, until we (hopefully) find a version that is free of that bug but still supports auto-increment. If that doesn't work, we can switch tests to file-based URLs.

    Andrus

    On Oct 9, 2010, at 6:23 PM, Michael Gentry wrote:
    Hi,

    I just did an experiment. Using H2 against a file (/tmp/CayenneTest)
    it worked fine (returned one record). Against an in memory DB it
    failed (returned 3 records). Seems like there is a bug in H2
    somewhere. Thoughts on how we should handle this?

    Thanks,

    mrg

    PS. Here is the SQL:


    CREATE TABLE ARTIST (ARTIST_ID BIGINT NOT NULL, ARTIST_NAME CHAR(254)
    NOT NULL, DATE_OF_BIRTH DATE NULL, PRIMARY KEY (ARTIST_ID));
    CREATE TABLE PAINTING (ARTIST_ID BIGINT NULL, ESTIMATED_PRICE
    DECIMAL(10, 2) NULL, GALLERY_ID INTEGER NULL, PAINTING_DESCRIPTION
    VARCHAR(255) NULL, PAINTING_ID INTEGER NOT NULL, PAINTING_TITLE
    VARCHAR(255) NOT NULL, PRIMARY KEY (PAINTING_ID));

    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33001, 'B');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33002, 'A');
    INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME) VALUES (33003, 'D');
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33009, 33001, 'X', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33010, 33001, 'Y', 5000);
    INSERT INTO PAINTING (PAINTING_ID, ARTIST_ID, PAINTING_TITLE,
    ESTIMATED_PRICE) VALUES (33011, 33002, 'Z', 5000);

    SELECT t0.DATE_OF_BIRTH AS ec0_0, t0.ARTIST_ID AS ec0_2,
    t0.ARTIST_NAME AS ec0_1 FROM ARTIST t0 LEFT OUTER JOIN PAINTING t1 ON
    (t0.ARTIST_ID = t1.ARTIST_ID) WHERE t1.PAINTING_ID IS NULL;
  • Andrus Adamchik at Oct 5, 2010 at 1:02 pm ⇧

    On Oct 5, 2010, at 3:49 PM, Michael Gentry wrote:

    INFO: Invalid connection key 'h2', trying default: internal_embedded_datasource
    Maybe we should throw an exception here, to be more explicit that a given key is invalid. Although since this happens within a single unit test, there's no clean way to abort the entire test suite (System.exit(1) or something ???).

    Andrus

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdev @
categoriescayenne
postedOct 4, '10 at 7:16p
activeOct 21, '10 at 3:24p
posts27
users2
websitecayenne.apache.org

2 users in discussion

Michael Gentry: 15 posts Andrus Adamchik: 12 posts

Content

People

Support

Translate

site design / logo © 2023 Grokbase