[hibernate-dev] hibernate mysql testsuite
I've already sent this, but got no answer. Please take a look at it. Take a look at the hibernate mysql tests: http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite There are much failings. As the testsuite was continually failing because of a mysql bug that is fixed in 4.1.18 I think it's worth installing newer version. Could you suggest which version will best suite your needs (4.1.latest, 5.0.latest)? btw. hibernate can be tested against innodb and myisam. Currently it is tested only against innodb. Is this ok? Thanks, Aleksandar Kostadinov ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] hibernate mysql testsuite
Aleksandar Kostadinov wrote: As the testsuite was continually failing because of a mysql bug that is fixed in 4.1.18 I think it's worth installing newer version. Have you got a reference to this bug ? Darryl ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] hibernate mysql testsuite
On Wed, 29 Nov 2006 10:10:46 +0100, Darryl Miles <[EMAIL PROTECTED]> wrote: Aleksandar Kostadinov wrote: As the testsuite was continually failing because of a mysql bug that is fixed in 4.1.18 I think it's worth installing newer version. Have you got a reference to this bug ? yes, knowing what that bug is would be beneficial. And regarding the version then Mysql 4.whateveristhelateststable sounds like the best match. Mysql 5 is still in beta, correct ? With respect to isam and innodb I would say that innodb is the important one since isam doesn't have proper tx isolation nor foreign key constraints and as such is not really something we want to encourage. -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss a division of Red Hat [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] hibernate mysql testsuite
Max Rydahl Andersen wrote: On Wed, 29 Nov 2006 10:10:46 +0100, Darryl Miles <[EMAIL PROTECTED]> wrote: Aleksandar Kostadinov wrote: As the testsuite was continually failing because of a mysql bug that is fixed in 4.1.18 I think it's worth installing newer version. Have you got a reference to this bug ? yes, knowing what that bug is would be beneficial. And regarding the version then Mysql 4.whateveristhelateststable sounds like the best match. Mysql 5 is still in beta, correct ? No. 5.0 went GA I guess 3rd Nov 2005. http://www.mysql.com/news-and-events/on-demand-webinars/mysql5.0-ga-2005-11-03.php But since we're in overlap period a Mysql 4.1.x server and 5.0.x server should still be considered mainstream (by me anyway). With respect to isam and innodb I would say that innodb is the important one since isam doesn't have proper tx isolation nor foreign key constraints and as such is not really something we want to encourage. Agreed. But I think the point he was making was that the same SQL server can be used to test both configurations and dialects. The cost of creating a new configuration and running a test isn't much extra as you already have the server setup. Even if such tests were done much less frequently, like once a week. While concentrating efforts on whatever version is the latest GA with all the major players. I'd have thought having access to a working SQL server from each vendor in each supported version series must be a useful resource just to have anyway. If you want pointers on installing/dual homing your test box with multiple MySQL servers drop me a mail. Darryl ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] hibernate mysql testsuite
On 11/29/06, Max Rydahl Andersen <[EMAIL PROTECTED]> wrote: And regarding the version then Mysql 4.whateveristhelateststable sounds like the best match. Mysql 5 is still in beta, correct ? MySQL 5.0 has been released for some time now (October 2005 -http://www.theserverside.com/news/thread.tss?thread_id=37248 ), currently at 5.0.27. MySQL 5.1 is still in beta Donnchadh With respect to isam and innodb I would say that innodb is the important one since isam doesn't have proper tx isolation nor foreign key constraints and as such is not really something we want to encourage. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] hibernate mysql testsuite
As the testsuite was continually failing because of a mysql bug that is fixed in 4.1.18 I think it's worth installing newer version. Have you got a reference to this bug ? yes, knowing what that bug is would be beneficial. And regarding the version then Mysql 4.whateveristhelateststable sounds like the best match. no bug ref still ? :) Mysql 5 is still in beta, correct ? No. 5.0 went GA I guess 3rd Nov 2005. ah - not so long ago then ;) I'd have thought having access to a working SQL server from each vendor in each supported version series must be a useful resource just to have anyway. If you want pointers on installing/dual homing your test box with multiple MySQL servers drop me a mail. I got too many different db installations to count on my box so i got it covered ;) -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss a division of Red Hat [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] hibernate mysql testsuite
Max Rydahl Andersen wrote: > > As the testsuite was continually failing because of a mysql bug > that is > fixed in 4.1.18 I think it's worth installing newer version. Have you got a reference to this bug ? >>> >>> yes, knowing what that bug is would be beneficial. >>> And regarding the version then Mysql 4.whateveristhelateststable >>> sounds like the best match. >> > > no bug ref still ? :) > There will not be ;) Sorry I've sent a note to Darryl and not to the list. I've lost the ref. I don't have even the error message now so it will be very hard to find it again. The bug is that there get tables created which cannot be dropped because of some temporary files incorrectly created. It is not a problem for now, but could appear in the future breaking any consequent tests. And this is why I think we need a newer version." >>> Mysql 5 is still in beta, correct ? >> >> >> No. 5.0 went GA I guess 3rd Nov 2005. > > > ah - not so long ago then ;) > >> I'd have thought having access to a working SQL server from each >> vendor in each supported version series must be a useful resource >> just to have anyway. If you want pointers on installing/dual homing >> your test box with multiple MySQL servers drop me a mail. > > > I got too many different db installations to count on my box so i got > it covered ;) So which version do you guys prefer and is the fail rate for the mysql tests normal? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] overriding target through annotations
I'm looking at ANN-422 In HA, the target is usually inferred from the API (generics), and can be overridden in all associations through targetEntity ( @ManyToOne(targetEntity...) ) currently, you cannot override the target for a component, nor you can override it for a Two solutions 1. Define a @Target annotation that will work like the targetEntity for association and also handle components (@Embedded) Define a @MapKeyTarget to override the or (composite-element) target 2. Define a @Target annotation that will work like the targetEntity for association and also handle components (@Embedded) add a targetElement to @MapKey and @MapKeyManyToMany annotations I don't like much 2 because it mixes physical concerns and logical ones, but it reduce the amount of needed annotations Note that I hope the future spec will hopefully handle all cases nicely (ie add a targetElement in @Embedded), @MapKey should go to back the drawing board from a spec POV so we can think of something clean from the begining. Any preference, or alternative solution? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] overriding target through annotations
On Nov 29, 2006, at 9:23 PM, Emmanuel Bernard wrote: Note that I hope the future spec will hopefully handle all cases nicely (ie add a targetElement in @Embedded), @MapKey should go to back the drawing board from a spec POV so we can think of something clean from the begining. I'm for 2., because @javax.persistence.MapKey is really completely useless and has to be redesigned (looks like a legacy case that one of the EG members had and thought that it would be useful). So enhance @org.hibernate.annotations.MapKey and create a @Target that works for @Embedded. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate-oracle10-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20061129215952 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:106: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:83: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 11/29/2006 21:59:52Time to build: 19 minutes 1 secondLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (953) Total Errors and Failures: (6)testSequenceIdentityGeneratororg.hibernate.test.generatedkeys.seqidentity.SequenceIdentityTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestManyToManyPropertyReforg.hibernate.test.propertyref.PropertyRefTesttestFetchInSubqueryFailureExpectedorg.hibernate.test.hql.ASTParserLoadingTesttestBoundedMaterializedBlobAccessorg.hibernate.test.lob.BlobTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 2297)10880modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/DenormalizedTable.javaANN-473 unique constraint on TABLE_PER_CLASS10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/configuration.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/basic_mapping.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/session_api.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/performance.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/query_sql.xmlremove black circle mark that is translator used.10871modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/ASTParserLoadingTest.javaadjusted test case for Ingres.10869modifiedepbernard//trunk/Hibernate3/src/org/hibernate/engine/query/ParameterParser.javaHHH-2264 Avoid NPE on user query error10864modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/impl/SessionFactoryImpl.javaHHH-2259 : jta current session + auto-flush10862modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/impl/SQLQueryImpl.javaHHH-2238 : SQLQuery.executeUpdate() + flush-modes10860modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/util/ExternalSessionFactoryConfig.javaHHH-2246 : mbean + cache-provider-config setting10860modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/jmx/HibernateServiceMBean.javaHHH-2246 : mbean + cache-provider-config setting10857modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/persister/entity/JoinedSubclassEntityPersister.javaHHH-2242 : optimisitc-locking=none on joined-subclass10857modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/engine/Versioning.javaHHH-2242 : optimisitc-locking=none on joined-subclass10857modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/tuple/entity/EntityMetamodel.javaHHH-2242 : optimisitc-locking=none on joined-subclass10856modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/impl/AbstractQueryImpl.javaHHH-2250 : Query.setEntity() with null entity10853modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/AllTests.javaHHH-1851 : add tests to AllTests10852modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/persister/entity/AbstractEntityPersister.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/LineItem.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/Person.javaHHH-1851 : relax special 'id' property handling10852modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/persister/entity/AbstractPropertyMapping.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/IdentifierPropertyReferencesTest.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/Order.javaHHH-1851 : relax special 'id' property handling10852modified[EMAIL PROTECTED]//trunk/Hibernate3/doc/reference/en/modules/query_hql.xmlHHH-1851 : relax special 'id' property handling10852modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/hql/ast/tree/DotNode.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/Mapping.hbm.xmlHHH-1851 : relax special 'id' property handling10852modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibe
[hibernate-dev] hibernate-hsqldb-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20061129221943 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:92: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:83: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 11/29/2006 22:19:43Time to build: 8 minutes 42 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (945) Total Errors and Failures: (5)testReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestManyToManyPropertyReforg.hibernate.test.propertyref.PropertyRefTesttestUnionSubclassorg.hibernate.test.unionsubclass2.UnionSubclassTesttestFetchInSubqueryFailureExpectedorg.hibernate.test.hql.ASTParserLoadingTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 2297)10880modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/DenormalizedTable.javaANN-473 unique constraint on TABLE_PER_CLASS10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/configuration.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/basic_mapping.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/session_api.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/performance.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/query_sql.xmlremove black circle mark that is translator used.10871modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/hql/ASTParserLoadingTest.javaadjusted test case for Ingres.10869modifiedepbernard//trunk/Hibernate3/src/org/hibernate/engine/query/ParameterParser.javaHHH-2264 Avoid NPE on user query error10864modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/impl/SessionFactoryImpl.javaHHH-2259 : jta current session + auto-flush10862modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/impl/SQLQueryImpl.javaHHH-2238 : SQLQuery.executeUpdate() + flush-modes10860modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/util/ExternalSessionFactoryConfig.javaHHH-2246 : mbean + cache-provider-config setting10860modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/jmx/HibernateServiceMBean.javaHHH-2246 : mbean + cache-provider-config setting10857modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/persister/entity/JoinedSubclassEntityPersister.javaHHH-2242 : optimisitc-locking=none on joined-subclass10857modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/engine/Versioning.javaHHH-2242 : optimisitc-locking=none on joined-subclass10857modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/tuple/entity/EntityMetamodel.javaHHH-2242 : optimisitc-locking=none on joined-subclass10856modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/impl/AbstractQueryImpl.javaHHH-2250 : Query.setEntity() with null entity10853modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/AllTests.javaHHH-1851 : add tests to AllTests10852modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/persister/entity/AbstractEntityPersister.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/LineItem.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/Person.javaHHH-1851 : relax special 'id' property handling10852modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/persister/entity/AbstractPropertyMapping.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/IdentifierPropertyReferencesTest.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/Order.javaHHH-1851 : relax special 'id' property handling10852modified[EMAIL PROTECTED]//trunk/Hibernate3/doc/reference/en/modules/query_hql.xmlHHH-1851 : relax special 'id' property handling10852modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/hql/ast/tree/DotNode.javaHHH-1851 : relax special 'id' property handling10852added[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/idprops/Mapping.hbm.xmlHHH-1851 : relax special 'id' property handling10852modified[EMAIL PROTECTED]//trunk/Hibernate3/test/org/hibernate/test/legacy/CustomPersister.javaHHH-1851 : relax special 'id' property handling10852mo
[hibernate-dev] hibernate-mysql-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20061129222920 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:127: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:83: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 11/29/2006 22:29:20Time to build: 34 minutes 18 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (943) Total Errors and Failures: (50)testComponentQueriesorg.hibernate.test.hql.ASTParserLoadingTesttestCollectionFetchWithDistinctionAndLimitorg.hibernate.test.hql.ASTParserLoadingTesttestTempTableGenerationIsolationorg.hibernate.test.hql.BulkManipulationTesttestBooleanHandlingorg.hibernate.test.hql.BulkManipulationTesttestSimpleInsertorg.hibernate.test.hql.BulkManipulationTesttestSimpleNativeSQLInsertorg.hibernate.test.hql.BulkManipulationTesttestInsertWithManyToOneorg.hibernate.test.hql.BulkManipulationTesttestInsertWithMismatchedTypesorg.hibernate.test.hql.BulkManipulationTesttestInsertIntoSuperclassPropertiesFailsorg.hibernate.test.hql.BulkManipulationTesttestInsertAcrossMappedJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateWithWhereExistsSubqueryorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnComponentorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnManyToOneorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnImplicitJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnAnimalorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnMammalorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullUnionSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateSetNullOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnJoinedSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteOnMappedJoinorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassAbstractRootorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassConcreteSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteUnionSubclassLeafSubclassorg.hibernate.test.hql.BulkManipulationTesttestDeleteWithMetadataWhereFragmentsorg.hibernate.test.hql.BulkManipulationTesttestDeleteRestrictedOnManyToOneorg.hibernate.test.hql.BulkManipulationTesttestScrollingJoinFetchesForwardorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesReverseorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestScrollingJoinFetchesPositioningorg.hibernate.test.hql.ScrollableCollectionFetchingTesttestWithClauseFailsWithFetchorg.hibernate.test.hql.WithClauseTesttestWithClauseorg.hibernate.test.hql.WithClauseTesttestInterfaceProxiesorg.hibernate.test.interfaceproxy.InterfaceProxyTesttestQueryorg.hibernate.test.legacy.FooBarTesttestOneToOneGeneratororg.hibernate.test.legacy.FooBarTesttestReachabilityorg.hibernate.test.legacy.FooBarTesttestVersionedCollectionsorg.hibernate.test.legacy.FooBarTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestOneToManyLinkTableorg.hibernate.test.onetomany.OneToManyTesttestManyToManyPropertyReforg.hibernate.test.propertyref.PropertyRefTesttestManualSynchronizationorg.hibernate.test.sql.GeneralTesttestAutoDetectAliasingorg.hibernate.test.sql.GeneralTesttestScalarStoredProcedureorg.hibernate.test.sql.MySQLTesttestParameterHandlingorg.hibernate.test.sql.MySQLTesttestEntityStoredProcedureorg.hibernate.test.sql.MySQLTesttestFiltersWithJoinedSubclassorg.hibernate.test.subclassfilter.JoinedSubclassFilterTesttestUnionSubclassorg.hibernate.test.unionsubclass2.UnionSubclassTesttestFetchInSubqueryFailureExpectedorg.hibernate.test.hql.ASTParserLoadingTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 2297)10880modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/DenormalizedTable.javaANN-473 unique constraint on TABLE_PER_CLASS10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/configuration.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/basic_mapping.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/session_api.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/Hibernate3/doc/reference/ja/modules/performance.xmlremove black circle mark that is translator used.10874modifiedhonma//trunk/H
Re: [hibernate-dev] overriding target through annotations
this would help on a related issue http://opensource.atlassian.com/projects/hibernate/browse/HHH-2268 which is about the problem of redundant methods in jdk5 when you have covariant methods (e.g. Object clone() in Object and Customer clone() in Customer) With respect to HHH-2268 we could also filter out the bridge methods (by checking if they are volatile or not), but wouldn't that prevent users from being able to annotate the covariant methods ?...or is the annotations available on both methods...i guess it needs testing. /max I'm looking at ANN-422 In HA, the target is usually inferred from the API (generics), and can be overridden in all associations through targetEntity ( @ManyToOne(targetEntity...) ) currently, you cannot override the target for a component, nor you can override it for a Two solutions 1. Define a @Target annotation that will work like the targetEntity for association and also handle components (@Embedded) Define a @MapKeyTarget to override the or (composite-element) target 2. Define a @Target annotation that will work like the targetEntity for association and also handle components (@Embedded) add a targetElement to @MapKey and @MapKeyManyToMany annotations I don't like much 2 because it mixes physical concerns and logical ones, but it reduce the amount of needed annotations Note that I hope the future spec will hopefully handle all cases nicely (ie add a targetElement in @Embedded), @MapKey should go to back the drawing board from a spec POV so we can think of something clean from the begining. Any preference, or alternative solution? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss a division of Red Hat [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
