[teiid-issues] [JBoss JIRA] (TEIID-2608) Increase pg odbc client compatibility

Wed Jul 31 10:41:26 EDT 2013

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

Steven Hawkins commented on TEIID-2608:
---------------------------------------

Added support for the items in the description.  The added column can change generated teiid ids, but that should not be considered a breaking change.

Cleaned up exception handling in CompletionListeners so that an unchecked exception is logged, but otherwise doesn't cause unexpected followup exceptions (such as attempting to send an error on ResultReceiver that has already sent its result).

A side issue that we have so far side stepped is that tools seem to expect to be able to use the table name as the alias name, which is problematic for names containing '.'.  e.g. "vdb"."schema"."foo.bar" as "foo.bar" - is not allowed by Teiid.  I don't know if we have a formal KI on this anywhere but the approach is generally to use unqualified teiid names during import.  This may be an issue though at some point with name uniqueness, so we may have to offer an import option for "odbc safe" names that replace '.' with '_' in the Teiid name.

At some point we may also want to re-target some of the set handling to our session variable support, rather than just the client handling.

> Increase pg odbc client compatibility
> -------------------------------------
>
>                 Key: TEIID-2608
>                 URL: https://issues.jboss.org/browse/TEIID-2608
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: ODBC
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.5
>
>
> Using a 9.0 level odbc client we see errors with the following:
> set x TO y - since we don't expect TO
> 'foo'::regclass - which is shorthand for an oid lookup
> pg_index.indpred - is used by some metadata queries

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira