[teiid-issues] [JBoss JIRA] Commented: (TEIID-1651) 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

Thu Jun 23 10:32:23 EDT 2011

    [ https://issues.jboss.org/browse/TEIID-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610697#comment-12610697 ] 

Steven Hawkins commented on TEIID-1651:
---------------------------------------

The default behavior for JDBC 4.0 should be true, not false.  The only reason to default to false would be to match the EDS 5.1 behavior, but that would actually be preserving a bug.  I would vote for defaulting to true with an entry in the release notes on setting to false.  Also where do you see that useJDBC4ColumnNameAndLabelSemantics is a spec property?  It seems that property key is just something used by db2 and related such as derby.  For example mysql uses useOldAliasMetadataBehavior.

Comparing to the db2 docs our old findColumn logic was based upon only column labels (which means that it wasn't quite inline with the spec), so there is no behavioral change there.

> 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