[teiid-issues] [JBoss JIRA] Resolved: (TEIID-140) Unique constrainsts should be checked in costing logic

Mon May 4 14:58:46 EDT 2009

     [ https://jira.jboss.org/jira/browse/TEIID-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-140.
----------------------------------

    Resolution: Rejected

The metadata function used in cost calculation does return both the unique and primary keys.

> Unique constrainsts should be checked in costing logic
> ------------------------------------------------------
>
>                 Key: TEIID-140
>                 URL: https://jira.jboss.org/jira/browse/TEIID-140
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>    Affects Versions: 6.x
>            Reporter: Steven Hawkins
>            Priority: Optional
>             Fix For: 6.x
>
>
> Defect Tracker #24750: Currently we only check primary key constraints in costing, however we should more generically check for uniqueness constraints.

-- 
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