[
https://issues.jboss.org/browse/TEIID-1651?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-1651:
-------------------------------------
I searched the JDBC 4.0 spec couple days ago, this is not mentioned anywhere in the spec.
As you mentioned this was only a work around in the db2 driver.
The confusing part is JDBC Client tools like Squirrel showed the Column Name as the header
in their UI, not sure if that a mistake or deliberate. Also Paul N, said even the Oracle
driver behaved in the old way as Teiid did.
Due to a change in the JDBC spec on how the use of "AS" in
the select statement will now be returned in the getColumnLabel of the ResultSetMetadata,
Teiid must provide backwards support
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1651
URL:
https://issues.jboss.org/browse/TEIID-1651
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.4.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Blocker
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).
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira