[ https://issues.jboss.org/browse/TEIID-1651?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-1651: ------------------------------- Description: Teiid has already applied a fix to support the JDBC spec change for when an alias is used in the select clause. The spec change says the "AS" name will now be returned when getColumnLabel() is called, instead of getColumnName(). Unfortunately, this breaks backwards compatibility. To resolve the issue, the JDBC driver, to provide support for backwards compatibility, can allow the user to specify the useJDBC4ColumnNameAndLabelSemantics=true (default is false) property on the url (this is the recommended spec property). (was: Teiid has already applied a fix to support the JDBC spec change for when an alias is used in the select clause. The spec change says the "AS" name will now be returned when getColumnLabel() is called, instead of getColumnName(). Unfortunately, this breaks backwards compatibility in 5.2 and any vendor/client that is using EDS and depending on metadata. To resolve the issue, the JDBC driver, to provide support for backwards compatibility, can allow the user to specify the useJDBC4ColumnNameAndLabelSemantics=true (default is false) property on the url (this is the recommended spec property). Therefore, for 5.2, the default for this property should be set to "TRUE", so that the user doesn't have to make any changes in order to expect the same behavior. I would recommend in a future major release (i.e., 6.0) this default be changed to the industry standard of "TRUE".) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira