[hibernate-dev] [Fwd: hibernate-mysql50-testsuite Build CompletedWith Testsuite Errors]

[Steve Ebersole]

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: hibernate-dev-bounces at lists.jboss.org
[mailto:hibernate-dev-bounces at lists.jboss.org] On Behalf Of Darryl Miles
Sent: Monday, December 04, 2006 9:54 AM
To: Aleksandar Kostadinov
Cc: hibernate-dev at 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 at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev