Query broken after update to 2.2.4

This query:

select ddt.ddtid as "ID DDT", date_format(ddt.data_creazione, "%d-%m-%Y %H:%i") as "Data Creaz.", ddt.creatore as "Creatore", ddt.provenienza as "Provenienza", concat(ddt.procedura, " ", ddt.loadnumber) as "Load Num.", ddt.status as "Status", ddt.numero_colli as "Colli", date_format(ddt.scadenza_inventory,"%d-%m-%Y %H:%i") as "Scad. Inventory" from ddt inner join procedure_sprint on ddt.procedura = procedure_sprint.nome_procedura where ddt.procedura IS NOT NULL && ddt.status IN ("Inventory","Inserimento") order by ddt.scadenza_inventory asc;

used to work like a charm but after upgrading from Servoy 2.2.3 to Servoy 2.2.4-02 it returns strange values in the columns costructed with formatted dates and concatenated values. This is the output of the query run from within Servoy:

ID DDT Data Creaz. Creatore Provenienza Load Num. Status Colli Scad. Inventory
3124 [B@52b87c bcallipari Mars Information Services International [B@ce05c8 Inventory 15 [B@dda5fc
3125 [B@bc8476 bcallipari KSB-Computek [B@9c63f8 Inventory 11 [B@674b4d

If the query is run on the backend (MySQL 4.1) directly it returns the correct values, this is the output from mysql client:

| ID DDT | Data Creaz.      | Creatore   | Provenienza                                     | Load Num. | Status      | Colli | Scad. Inventory  |
+--------+------------------+------------+-------------------------------------------------+-----------+-------------+-------+------------------+
|   3124 | 28-04-2005 18:13 | bcallipari | Mars Information Services International         | CLD 1     | Inventory   |    15 | 30-04-2005 00:00 |
|   3125 | 29-04-2005 15:43 | bcallipari | KSB-Computek                                    | CLD 3     | Inventory   |    11 | 01-05-2005 15:43

The strange thing is that this is happening only on my production server (Linux, java 1.4.2-10b03, Servoy 2.2.4-02) and not in my Developer (MacOSX 10.4.5, java 1.5.0_05-48) nor in my test server (MacOSX 10.4.5, java 1.5.0_05-48). It happens with Mac and Windows clients running both Java 1.4.2 and Java 1.5.

Any hints?

Solved by downgrading the JDBC driver from mysql-connector-java-3.1.12-bin.jar to mysql-connector-java-3.1.8-bin.jar. Seems like MySQL 4.1.x doesn’t like this new driver (with MySQL 5 everything is fine).

Dev team, can you shed some light on what is happening so that I can file a bug report to MySQL dev team? Actually I don’t know how to report this thing…

Solved by downgrading the JDBC driver from mysql-connector-java-3.1.12-bin.jar to mysql-connector-java-3.1.8-bin.jar

Strange, on OS X nothing worked for me since MySQL 4.1 and below mysql-connector-java-3.1.12. :?

IT2BE:

Solved by downgrading the JDBC driver from mysql-connector-java-3.1.12-bin.jar to mysql-connector-java-3.1.8-bin.jar

Strange, on OS X nothing worked for me since MySQL 4.1 and below mysql-connector-java-3.1.12. :?

JDBC 3.1.12 works ok for me on MacOS X and MySQL 4.1.14 but on Linux and MySQL 4.1.10 I have that issue.
Looking at the MySQL bug reporting system I’ve seen that bug was resolved in 3.1.8 but is resurfacing now with 3.1.12, someone already filed the bug report.