On Mon, 28 Nov 2005 16:53:08 +0100, Steve Ebersole
<[EMAIL PROTECTED]> wrote:
A. You'd get the non-expanded SQL strings. For example "from Animal
where description in (:descList)" would return something like "select
... from animal animal0_ where animal0_.description in (?)"
Which is ju
A. You'd get the non-expanded SQL strings. For example "from Animal where
description in (:descList)" would return something like "select ... from animal
animal0_ where animal0_.description in (?)"
B. I think that's the reason for the '_' character ;)
-Original Message-
From: Max Ande
On Mon, 28 Nov 2005 16:11:21 +0100, Steve Ebersole
<[EMAIL PROTECTED]> wrote:
So some things to consider then:
A. You will only really, truly be able to get the SQL(s) after all
parameters values are known (accounting for parameter-lists)
And if I call getSQLStatements before parameters a
So some things to consider then:
A. You will only really, truly be able to get the SQL(s) after all parameters
values are known (accounting for parameter-lists)
B. Parameter-lists will again cause you problems here. This is because the
original parameter name is no longer known by the time the
You might want to change whatever you are doing to just run the AllTests
suite, which excludes a bunch of things.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan
Campbell
Sent: Monday, November 28, 2005 8:39 AM
To: Christian Bauer
Cc: Hibernate devel
Ryan Campbell wrote:
There were at least two which were taking > 200 seconds. I have lost
the results I used to give you this total.
The mysql and oracle runs are taking about 20 minutes each (total).
timesten is taking about an hour. SQL server (jtds) and Sybase
(jconnect) are both timing o
Can you give me the connection info to the various db instances? I'll
try running these manually and see how long things are taking. Or have
you tried this already?
With Oracle for example, it is pretty important how the underlying
database is setup in terms of how fast/slow the testsuite runs.
Also, there is the problem that Steve and I saw with the
org.hibernate.test.legacy.PerformanceTest. It does not have a finally
block for closing resources in case of error, and some databases will
hang when the hibernate test case attempts to drop a table which has
transactions still open against
There were at least two which were taking > 200 seconds. I have lost
the results I used to give you this total.
The mysql and oracle runs are taking about 20 minutes each (total).
timesten is taking about an hour. SQL server (jtds) and Sybase
(jconnect) are both timing out completely because th
Ryan Campbell wrote:
Can there be a timeout for the tests? I'm seeing tests hang against
different databases. If there was a timeout for the junit tests, these
hanging tests would be reported as failures.
I ran the tests on MySQL, and the longest one was 255 seconds, so
perhaps 500 seconds is
10 matches
Mail list logo
