[teiid-issues] [JBoss JIRA] Commented: (TEIID-203) Make connector capabilites more granular.

Mon May 4 15:58:47 EDT 2009

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

Steven Hawkins commented on TEIID-203:
--------------------------------------

To support reference and multi-select picklists, the easiest path would be to check pushdown element metadata for searchability.  A column should not be used in sort (distinct/non-all setquery/group by) unless it is marked as SEARCHABLE=SEARCHABLE|ALL_EXCEPT_LIKE.  Reference and multi-select picklists would then be marked as SUPPORTS_LIKE, which would tell use not to pushdown operations that involve ordered comparisions, but we would allow = and <> since it is implied by like.  

> Make connector capabilites more granular.
> -----------------------------------------
>
>                 Key: TEIID-203
>                 URL: https://jira.jboss.org/jira/browse/TEIID-203
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Connector API, Query Engine
>    Affects Versions: 6.0.0
>            Reporter: John Doyle
>            Assignee: Steven Hawkins
>             Fix For: 6.1.0
>
>
> Some connector capabilites are only available in combination with others.  For example, if you wish to support the SupportsAggregatesCount capability, you have to also support the SupportsAggregates capability(GROUP BY and HAVING).  This requirement creates additional requirements for a connector where the source syustem cabilities do not correspond with the relationships we have defined between capabilites.
> For instance, the SQL supported by salesforce can include the count(*) function, but it does not support GROUP BY or HAVING.  Because we require c connector to support SupportsAggregates befrore it can support count(*), the connector is required to implement those functions if it wishes to pus down count(*).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira