[hibernate-dev] FlushMode.NEVER deprecated
Hi. I can see in Hibernate 3.2 LockMode.NEVER is deprecated in favor of LockMode.MANUAL. Maybe this is a silly argument... but i think that FlushMode.NEVER has some "semantic" benefits. I mean, if i'm reading code and see session.setFlushMode(FlushMode.NEVER) i think "oh, this is going to be a read-only session". On the other hand, if i see session.setFlushMode(FlushMode.MANUAL) i'll think "oh, in this session the developer is going to manually flush the session at some point, instead of letting hibernate taking care". Even more, hibernate could throw some "Not flushable session (read-only)" exception if someone try to flush on this mode... -- -=-=-=-=-=-=-=-=-=-=-=-=- Andrés González. http://coyotevil.blogspot.com ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]
Is it possible to emit some extra information with the testsuite output
summary.
The host running the testsuites JDK and Operating System (whichever
values seems more useful across the major JDK) :
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=1.5.0_08-b03
java.specification.version=1.5
java.vendor=Sun Microsystems Inc.
java.version=1.5.0_08
os.arch=amd64
os.name=Linux
os.version=2.6.18
Infact the above is hidden away in host-version-info.txt, but surely the
above information can be summarized into a single line and emitted with
the test suite for all to clearly see.
Java(TM) 2 Runtime Environment, Standard Edition (1.5.0_08) Sun
Microsystems Inc. [Linux amd64 2.6.18]
"java.runtime.name" ("java.version") "java.vendor" ["os.name" "os.arch"
"os.version"]
Also the same with the exact SQL server version and the JDBC driver
version, maybe also a new "jdbc-version-info.txt" should be created too:
On MySQL a 'SELECT VERSION();' gets the server version but a more
generic way maybe to use:
java.sql.Connection.getServerMajorVersion() = 5
java.sql.Connection.getServerMinorVersion() = 0
java.sql.Connection.getSubMinorVersion() = 22
java.sql.Connection.getServerVersion() = "MySQL, version:
5.0.27-standard-log" ??
java.sql.Driver.getMajorVersion() = "3"
java.sql.Driver.getMinorVersion() = "1"
java.sql.Connection.getMetaData().getDriverVersion() = "MySQL-AB JDBC
Driver, version: mysql-connector-java-3.1.10 ( $Date: 2005/05/19
15:52:23 $, $Revision: 1.1.2.2 $ )"
Looking at your test suite you are running with 3.1.10 JDBC driver, I
know for sure that 3.1.13 is buggy with hibernate as I had to upgrade
from it. This was in relation to unsigned data handling into signed
java types (UNSIGNED TINYINT (0-255) -> short). Please consider 3.1.14
or later.
Also JDBC driver 5.0.x is considered GA now looking at the MySQL
website. Is the 5.0.x driver a necessary upgrade to get access to some
of the features of the 5.0.x MySQL server ? I would recommend maybe
using mysql-connector-java-5.0.x with MySQL 5.0.x.
Darryl
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build Completed With Testsuite Errors]
Darryl,
For the information you wish, you could create a JIRA task (maybe a
feature request).
I will update the the JDBC driver to the latest.
Tanks for the feedback.
Aleksandar
Darryl Miles wrote:
>
> Is it possible to emit some extra information with the testsuite
> output summary.
>
>
>
> The host running the testsuites JDK and Operating System (whichever
> values seems more useful across the major JDK) :
>
> java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
> java.runtime.version=1.5.0_08-b03
> java.specification.version=1.5
> java.vendor=Sun Microsystems Inc.
> java.version=1.5.0_08
> os.arch=amd64
> os.name=Linux
> os.version=2.6.18
>
>
> Infact the above is hidden away in host-version-info.txt, but surely
> the above information can be summarized into a single line and emitted
> with the test suite for all to clearly see.
>
> Java(TM) 2 Runtime Environment, Standard Edition (1.5.0_08) Sun
> Microsystems Inc. [Linux amd64 2.6.18]
>
> "java.runtime.name" ("java.version") "java.vendor" ["os.name"
> "os.arch" "os.version"]
>
>
>
>
> Also the same with the exact SQL server version and the JDBC driver
> version, maybe also a new "jdbc-version-info.txt" should be created too:
>
> On MySQL a 'SELECT VERSION();' gets the server version but a more
> generic way maybe to use:
>
> java.sql.Connection.getServerMajorVersion() = 5
> java.sql.Connection.getServerMinorVersion() = 0
> java.sql.Connection.getSubMinorVersion() = 22
> java.sql.Connection.getServerVersion() = "MySQL, version:
> 5.0.27-standard-log" ??
>
> java.sql.Driver.getMajorVersion() = "3"
> java.sql.Driver.getMinorVersion() = "1"
>
> java.sql.Connection.getMetaData().getDriverVersion() = "MySQL-AB JDBC
> Driver, version: mysql-connector-java-3.1.10 ( $Date: 2005/05/19
> 15:52:23 $, $Revision: 1.1.2.2 $ )"
>
>
>
> Looking at your test suite you are running with 3.1.10 JDBC driver, I
> know for sure that 3.1.13 is buggy with hibernate as I had to upgrade
> from it. This was in relation to unsigned data handling into signed
> java types (UNSIGNED TINYINT (0-255) -> short). Please consider
> 3.1.14 or later.
>
> Also JDBC driver 5.0.x is considered GA now looking at the MySQL
> website. Is the 5.0.x driver a necessary upgrade to get access to
> some of the features of the 5.0.x MySQL server ? I would recommend
> maybe using mysql-connector-java-5.0.x with MySQL 5.0.x.
>
>
> Darryl
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] FlushMode.NEVER deprecated
andresgr wrote: Hi. I can see in Hibernate 3.2 LockMode.NEVER is deprecated in favor of LockMode.MANUAL. Maybe this is a silly argument... but i think that FlushMode.NEVER has some "semantic" benefits. I mean, if i'm reading code and see session.setFlushMode(FlushMode.NEVER) i think "oh, this is going to be a read-only session". On the other hand, if i see session.setFlushMode(FlushMode.MANUAL) i'll think "oh, in this session the developer is going to manually flush the session at some point, instead of letting hibernate taking care". Even more, hibernate could throw some "Not flushable session (read-only)" exception if someone try to flush on this mode... This is exactly why MANUAL is a better name than NEVER :-) ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
RE: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]
I am not really familiar with CruiseControl, so what exactly do you mean
by "emit"?
AFAIK, the same box hosts the various runs, correct? So unless there
are plans to change that, a lot of effort here seems silly.
As far as the extra JDBC metadata, the JDBC driver is *supposed* to make
this info available via the DatabaseMetadata; be warned not all
Connection impls do a good job of this. At any rate, Hibernate logs
this info during SessionFactory initialization (in the testsuite's
hibernate.log output):
10:57:31,981 INFO SettingsFactory:81 - RDBMS: MySQL, version:
5.0.27-community-nt
10:57:31,981 INFO SettingsFactory:82 - JDBC driver: MySQL-AB JDBC
Driver, version: mysql-connector-java-5.0.4 ( $Date: 2006-10-19 17:47:48
+0200 (Thu, 19 Oct 2006) $, $Revision: 5908 $ )
1
(these are from my local setup).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darryl Miles
Sent: Monday, December 04, 2006 9:54 AM
To: Aleksandar Kostadinov
Cc: hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build
CompletedWith Testsuite Errors]
Is it possible to emit some extra information with the testsuite output
summary.
The host running the testsuites JDK and Operating System (whichever
values seems more useful across the major JDK) :
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=1.5.0_08-b03
java.specification.version=1.5
java.vendor=Sun Microsystems Inc.
java.version=1.5.0_08
os.arch=amd64
os.name=Linux
os.version=2.6.18
Infact the above is hidden away in host-version-info.txt, but surely the
above information can be summarized into a single line and emitted with
the test suite for all to clearly see.
Java(TM) 2 Runtime Environment, Standard Edition (1.5.0_08) Sun
Microsystems Inc. [Linux amd64 2.6.18]
"java.runtime.name" ("java.version") "java.vendor" ["os.name" "os.arch"
"os.version"]
Also the same with the exact SQL server version and the JDBC driver
version, maybe also a new "jdbc-version-info.txt" should be created too:
On MySQL a 'SELECT VERSION();' gets the server version but a more
generic way maybe to use:
java.sql.Connection.getServerMajorVersion() = 5
java.sql.Connection.getServerMinorVersion() = 0
java.sql.Connection.getSubMinorVersion() = 22
java.sql.Connection.getServerVersion() = "MySQL, version:
5.0.27-standard-log" ??
java.sql.Driver.getMajorVersion() = "3"
java.sql.Driver.getMinorVersion() = "1"
java.sql.Connection.getMetaData().getDriverVersion() = "MySQL-AB JDBC
Driver, version: mysql-connector-java-3.1.10 ( $Date: 2005/05/19
15:52:23 $, $Revision: 1.1.2.2 $ )"
Looking at your test suite you are running with 3.1.10 JDBC driver, I
know for sure that 3.1.13 is buggy with hibernate as I had to upgrade
from it. This was in relation to unsigned data handling into signed
java types (UNSIGNED TINYINT (0-255) -> short). Please consider 3.1.14
or later.
Also JDBC driver 5.0.x is considered GA now looking at the MySQL
website. Is the 5.0.x driver a necessary upgrade to get access to some
of the features of the 5.0.x MySQL server ? I would recommend maybe
using mysql-connector-java-5.0.x with MySQL 5.0.x.
Darryl
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
RE: [hibernate-dev] FlushMode.NEVER deprecated
Thanks for highlighting exactly why FlushMode.NEVER was poorly named ;) I believe you are actually asking for FlushMode.NEVER to actually be migrated to a new semantic. That's not a good idea because it would be confusing for users on an upgrade... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of andresgr Sent: Monday, December 04, 2006 9:36 AM To: hibernate-dev@lists.jboss.org Subject: [hibernate-dev] FlushMode.NEVER deprecated Hi. I can see in Hibernate 3.2 LockMode.NEVER is deprecated in favor of LockMode.MANUAL. Maybe this is a silly argument... but i think that FlushMode.NEVER has some "semantic" benefits. I mean, if i'm reading code and see session.setFlushMode(FlushMode.NEVER) i think "oh, this is going to be a read-only session". On the other hand, if i see session.setFlushMode(FlushMode.MANUAL) i'll think "oh, in this session the developer is going to manually flush the session at some point, instead of letting hibernate taking care". Even more, hibernate could throw some "Not flushable session (read-only)" exception if someone try to flush on this mode... -- -=-=-=-=-=-=-=-=-=-=-=-=- Andrés González. http://coyotevil.blogspot.com ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]
Steve Ebersole wrote: I am not really familiar with CruiseControl, so what exactly do you mean by "emit"? emit in this case means make it clearly visible at first glance which JDK, Host, JDBC Driver and SQL Server version are being used for the test case run. That seems like a pretty basic requirement to me. AFAIK, the same box hosts the various runs, correct? So unless there are plans to change that, a lot of effort here seems silly. This presumes everybody with an interest in the test results generated from that box is also kept in the loop with all future changes and upgrades of that box. This presumes that the person responsible for maintaining the testing box understands all the implications of interactions with the various versions of the components used in the tests. I'm surprised you think what should amount to a couple of out.println() statements is "a lot of effort". For example Max wasn't aware 5.0 has gone GA, well it if was clear from looking at the test summary what was actually being tested someone with a better knowledge could have pointed something like that out. I don't expect everyone to know everything about everything and I also don't expect everyone to go digging at the sight of every test failure. So if something can be done to make the test results a more accurate picture of where things stand is a good thing by me. YMMV (these are from my local setup). Great, but of little relevance to the daily testing emailed to the devel list. Darryl ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
RE: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]
Um, perhaps if you are going to ask me to do something you could can the attitude? Seems like a basic requirement to me... As far as the box hosting the runs, I did not realize I had presumed anything. The point was simply that it seems silly to me to invest a lot of effort to script this when this could simply be hard-coded info since they all run on the same exact env. Is it as easy as a couple of printlns? I don't know (again see my qualification that I do not know CruiseControl). BTW, nothing is a lot of effort when someone else is doing all the work ;) So Max was not aware that MySQL 5.0 had gone GA. How exactly would us making these things you ask for more accessible in our testsuite results have changed that? I am simply telling Aleksandar that if this takes a lot of effort that I would much prefer him instead continuing to focus his efforts on getting more database coverage up and running. You don't agree with that? Great! Let us know when you have your hosted Hibernate test suite up and running; then you can call the shots. But to me I am more interested in the coverage; I can live with 4 clicks to get this other info in the meantime. -Original Message- From: Darryl Miles [mailto:[EMAIL PROTECTED] Sent: Monday, December 04, 2006 11:40 AM To: Steve Ebersole Cc: Aleksandar Kostadinov; hibernate-dev@lists.jboss.org Subject: Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors] Steve Ebersole wrote: > I am not really familiar with CruiseControl, so what exactly do you mean > by "emit"? emit in this case means make it clearly visible at first glance which JDK, Host, JDBC Driver and SQL Server version are being used for the test case run. That seems like a pretty basic requirement to me. > AFAIK, the same box hosts the various runs, correct? So unless there > are plans to change that, a lot of effort here seems silly. This presumes everybody with an interest in the test results generated from that box is also kept in the loop with all future changes and upgrades of that box. This presumes that the person responsible for maintaining the testing box understands all the implications of interactions with the various versions of the components used in the tests. I'm surprised you think what should amount to a couple of out.println() statements is "a lot of effort". For example Max wasn't aware 5.0 has gone GA, well it if was clear from looking at the test summary what was actually being tested someone with a better knowledge could have pointed something like that out. I don't expect everyone to know everything about everything and I also don't expect everyone to go digging at the sight of every test failure. So if something can be done to make the test results a more accurate picture of where things stand is a good thing by me. YMMV > (these are from my local setup). Great, but of little relevance to the daily testing emailed to the devel list. Darryl ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]
Steve Ebersole wrote: > Um, perhaps if you are going to ask me to do something you could can the > attitude? Seems like a basic requirement to me... Sorry if I put words in your mouth there or seem to be creating lots of work for somebody else. Is the cruise control configuration / testing regime checked into a repository; maybe I can assist with these changes and attach a patch rather than open a JIRA feature request ? Darryl ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] overriding target through annotations
I agree with your analysis, but @MapKeyTarget vs @o.h.a.MapKey / @o.h.a.MapKeyManyToMany enhancement with target is not influenced by the @j.p.MapKey design flaws. Pros of each solution are 1. @MapKeyTarget SoC (Relational descriptions are split from Object descriptions in annotations) @Target and @MapKeyTarget are consistent 2. no @MapKeyTarget No extra @MapKeyTarget annotation Christian Bauer wrote: 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 mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate-mysql-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20061204151821 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: 12/04/2006 15:18:21Time to build: 35 minutes 3 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (943) Total Errors and Failures: (51)testDom4jorg.hibernate.test.dom4j.Dom4jTesttestMapIndexEmisionorg.hibernate.test.dom4j.Dom4jTesttestCollectionFetchWithDistinctionAndLimitorg.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.OneToManyTesttestPaginationorg.hibernate.test.pagination.PaginationTesttestManyToManyPropertyReforg.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.JoinedSubclassFilterTesttestFetchInSubqueryFailureExpectedorg.hibernate.test.hql.ASTParserLoadingTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 2301)10905modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/PersistentClass.javaANN-425 Property not found when defined in a @IdClass and referenced by a @OneToManyANN-499 @IdClass and @ManyToOne leads to repeated column exception10900modifiedepbernard//trunk/Hibernate3/src/org/hibernate/persister/collection/AbstractCollectionPersister.javaHHH-227510897modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/Collection.javaHHH-2274 use ordered collection when manyToManyOrderBy is used10884modifiedhonma//trunk/Hibernate3/doc/reference/build.xmli duplicated comment out line of ja in all.doc target.10880modifiedepbernard//trunk
[hibernate-dev] hibernate-mysql50-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql50-testsuite?log=log20061204144847 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:134: 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: 12/04/2006 14:48:47Time to build: 28 minutes 46 seconds Unit Tests: (943) Total Errors and Failures: (47)testCollectionFetchWithDistinctionAndLimitorg.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.GeneralTesttestHandSQLorg.hibernate.test.sql.MySQLTesttestEntityStoredProcedureorg.hibernate.test.sql.MySQLTesttestFiltersWithJoinedSubclassorg.hibernate.test.subclassfilter.JoinedSubclassFilterTesttestFetchInSubqueryFailureExpectedorg.hibernate.test.hql.ASTParserLoadingTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 0) ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate-hsqldb-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20061204220009 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: 12/04/2006 22:00:09Time to build: 9 minutes 19 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 2302)10916modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/Session.javajavadocs10905modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/PersistentClass.javaANN-425 Property not found when defined in a @IdClass and referenced by a @OneToManyANN-499 @IdClass and @ManyToOne leads to repeated column exception10900modifiedepbernard//trunk/Hibernate3/src/org/hibernate/persister/collection/AbstractCollectionPersister.javaHHH-227510897modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/Collection.javaHHH-2274 use ordered collection when manyToManyOrderBy is used10884modifiedhonma//trunk/Hibernate3/doc/reference/build.xmli duplicated comment out line of ja in all.doc target.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 handli
[hibernate-dev] hibernate-mysql50-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql50-testsuite?log=log20061204221023 TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:134: 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: 12/04/2006 22:10:23Time to build: 26 minutes 45 secondsLast changed: 12/04/2006 15:39:04Last log entry: javadocs Unit Tests: (943) Total Errors and Failures: (47)testCollectionFetchWithDistinctionAndLimitorg.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.GeneralTesttestHandSQLorg.hibernate.test.sql.MySQLTesttestEntityStoredProcedureorg.hibernate.test.sql.MySQLTesttestFiltersWithJoinedSubclassorg.hibernate.test.subclassfilter.JoinedSubclassFilterTesttestFetchInSubqueryFailureExpectedorg.hibernate.test.hql.ASTParserLoadingTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 1)10916modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/Session.javajavadocs ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] hibernate-mysql-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20061204223744 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: 12/04/2006 22:37:44Time to build: 34 minutes 21 secondsLast changed: 12/31/2005 20:44:14Last log entry: less noisy Unit Tests: (943) Total Errors and Failures: (51)testDom4jorg.hibernate.test.dom4j.Dom4jTesttestMapIndexEmisionorg.hibernate.test.dom4j.Dom4jTesttestCollectionFetchWithDistinctionAndLimitorg.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.OneToManyTesttestPaginationorg.hibernate.test.pagination.PaginationTesttestManyToManyPropertyReforg.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.JoinedSubclassFilterTesttestFetchInSubqueryFailureExpectedorg.hibernate.test.hql.ASTParserLoadingTesttestJoinFetchPropertyReforg.hibernate.test.propertyref.PropertyRefTest Modifications since last build: (first 50 of 2302)10916modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/Session.javajavadocs10905modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/PersistentClass.javaANN-425 Property not found when defined in a @IdClass and referenced by a @OneToManyANN-499 @IdClass and @ManyToOne leads to repeated column exception10900modifiedepbernard//trunk/Hibernate3/src/org/hibernate/persister/collection/AbstractCollectionPersister.javaHHH-227510897modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/Collection.javaHHH-2274 use ordered collection when manyToManyOrderBy is used10884modifiedhonma//trunk/Hibernate3/doc/reference/build.
[hibernate-dev] hibernate-oracle10-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20061204231257 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: 12/04/2006 23:12:57Time to build: 17 minutes 20 secondsLast 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 2302)10916modified[EMAIL PROTECTED]//trunk/Hibernate3/src/org/hibernate/Session.javajavadocs10905modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/PersistentClass.javaANN-425 Property not found when defined in a @IdClass and referenced by a @OneToManyANN-499 @IdClass and @ManyToOne leads to repeated column exception10900modifiedepbernard//trunk/Hibernate3/src/org/hibernate/persister/collection/AbstractCollectionPersister.javaHHH-227510897modifiedepbernard//trunk/Hibernate3/src/org/hibernate/mapping/Collection.javaHHH-2274 use ordered collection when manyToManyOrderBy is used10884modifiedhonma//trunk/Hibernate3/doc/reference/build.xmli duplicated comment out line of ja in all.doc target.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/t
