View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sybase-testsuite?log=log20060523013504
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:05/23/2006 01:35:04Time to build:
Unit Tests: (0) Total Errors and Failures:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-mysql-testsuite?log=log20060523044328
TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:121: The following error occurred while executing this line:
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20060523052210
TESTS FAILEDAnt Error Message:/home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:100: The following error occurred while executing this line:
Problem definition:
javax.persistence.Query interface has not defined typed setPrarameter
methods.
There exists valid queries that can't be parametrized properly via
methods in javax.persistence.Query.
details:
in java.sql.PreparedStatement exists only two method for setting null
values,
I think you are looking for [EMAIL PROTECTED] But kind of hard
for them to change the persistence spec to add type to the
setParameter() methods when JPA does not even have a notion of a type.
So in your Hibernate request(s), then how do you propose that we allow
users to bind parameters of
Steve Ebersole wrote:
I think you are looking for [EMAIL PROTECTED]
May be, but in my opinion it is a common problem.
But kind of hard
for them to change the persistence spec to add type to the
setParameter() methods when JPA does not even have a notion of a type.
try realize select
Perhaps it is a common problem, but one that stems from an interface
defined by JSR-220. Guess what, Hibernate does not control the
definition of that interface. Thus, whether you choose to believe it or
not, such comments need to be directed at previously mentioned mailing
list.
As for your
