JDBC 3.5 compliance 2006-10-14 - By Markus KARG
Back
On the MySQL web site it is told that MaxDB's JDBC driver would be JDBC
compliant. In fact, to fulfil this, the JDBC escape syntax must be
supported. This is not the case, as you easily can test:
s.execute("CREATE TABLE T1(F1 INTEGER, PRIMARY KEY (F1))");
s.execute("CREATE TABLE T2(F2 INTEGER, PRIMARY KEY (F2), FOREIGN KEY FK
(F2) REFERENCES T1 (F1) ON DELETE CASCADE)");
s.execute("SELECT * FROM T1 LEFT OUTER JOIN T2 ON T1.F1=T2.F2");
s.execute("SELECT * FROM T1 {oj LEFT OUTER JOIN T2 ON T1.F1=T2.F2}");
The first SELECT command is working well, the second one complains about
this: [-3008] (at 18): Invalid keyword or missing delimiter.
So to fulfil "real" JDBC compliance, this should be fixed. Unfortunately
I did not find any bug tracker or email address where to send a bug report.
Can anybody tell me where to complain about this insufficiency?
Thanks
Markus
|
|
