Skip navigation links
MySQL Connector/J Developer's Guide :: 3 Connector/J Installation :: 3.3 Upgrading from an Older Version
3.3.1 Upgrading to MySQL Connector/J 5.1.x »
Section Navigation      [Toggle]

3.3. Upgrading from an Older Version

[+/-]

3.3.1. Upgrading to MySQL Connector/J 5.1.x
3.3.2. JDBC-Specific Issues When Upgrading to MySQL Server 4.1 or Newer
3.3.3. Upgrading from MySQL Connector/J 3.0 to 3.1

This section has information for users who are upgrading from one version of Connector/J to another, or to a new version of the MySQL server that supports a more recent level of JDBC. A newer version of Connector/J might include changes to support new features, improve existing functionality, or comply with new standards.

Copyright © 1997, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices

User Comments

Posted by ivan Shevchenko on September 25 2011 3:05pm[Delete] [Edit]

jdbc:mysql://localhost:3306/table_name?useOldAliasMetadataBehavior=true&useOldAliasMetadataBehaviour=true

I don't know why but jdbc 5.1.17 works with queries like

SELECT q_eu.q_dt as dt, q_eu.open as eu FROM eu__15 as q_eu WHERE q_eu.q_dt >"1999.01.01" ORDER BY q_eu.q_dt LIMIT 0,100

with such paradox syntax ONLY. I have lost a lot of blood.

useOldAliasMetadataBehavior
useOldAliasMetadataBehaviour
nice Aliaces!

Add your own comment.