[Fwd: hibernate-sqlserver-jtds-testsuite Build Completed With Testsuite Errors]
by Aleksandar Kostadinov
Hi. As you see I used jtds driver for this one. It doesn't support
setting the transaction isolation level to snapshot, but I tuned the
database this way:
ALTER DATABASE cruisecontrol SET ALLOW_SNAPSHOT_ISOLATION ON;
ALTER DATABASE cruisecontrol SET READ_COMMITTED_SNAPSHOT ON;
This should set the default isolation level to snapshot.
When I runned the tests with the MS jdbc driver I got one more error
than with the jdts driver. It is
org.hibernate.test.legacy.MasterDetailTest.testCachedCollectionRefresh.
But I'm not sure in the results as the cruesecintrol builds give half
the errors of these I've got from the mentioned tests.
So to conclude see if you see the results consistent with your local
tests. I'll modify the build if you do not like the jtds driver or
something else.
18 years
RE: oracle test results
by Steve Ebersole
Sweet, thanks!
-----Original Message-----
From: Aleksandar Kostadinov [mailto:akostadinov@jboss.org]
Sent: Thursday, December 07, 2006 10:05 AM
To: Steve Ebersole
Cc: hibernate-dev(a)lists.jboss.org
Subject: Re: oracle test results
I've updated the driver to 10.2.0.2
You should be able to see the new results in half an hour.
Steve Ebersole wrote:
>OK, I just tracked down the cause of the failures I found disturbing
>with the hibernate-oracle-10g testsuite. Y'all are using a much older
>driver:
>22:32:44,850 INFO SettingsFactory:82 - JDBC driver: Oracle JDBC
driver,
>version: 10.1.0.3.0
>
>We should be using some 10.2.x series driver. Locally I use
10.2.0.1.0;
>they are up to 10.2.0.2 (either of which should work):
>http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.htm
l
>
>This is the cause (I believe) for failures in:
>org.hibernate.test.lob.BlobTest#testBoundedMaterializedBlobAccess
>org.hibernate.test.generatedkeys.seqidentity.SequenceIdentityTest#testS
e
>quenceIdentityGenerator
>
>
18 years
Re: oracle test results
by Aleksandar Kostadinov
I've updated the driver to 10.2.0.2
You should be able to see the new results in half an hour.
Steve Ebersole wrote:
>OK, I just tracked down the cause of the failures I found disturbing
>with the hibernate-oracle-10g testsuite. Y'all are using a much older
>driver:
>22:32:44,850 INFO SettingsFactory:82 - JDBC driver: Oracle JDBC driver,
>version: 10.1.0.3.0
>
>We should be using some 10.2.x series driver. Locally I use 10.2.0.1.0;
>they are up to 10.2.0.2 (either of which should work):
>http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
>
>This is the cause (I believe) for failures in:
>org.hibernate.test.lob.BlobTest#testBoundedMaterializedBlobAccess
>org.hibernate.test.generatedkeys.seqidentity.SequenceIdentityTest#testSe
>quenceIdentityGenerator
>
>
18 years
overriding target through annotations
by Emmanuel Bernard
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 <map-key-many-to-many/>
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 <map-key-many-to-many/> or
<map-key/> (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?
18 years
