[teiid-issues] [JBoss JIRA] (TEIID-2263) makedep makenotdep hints should allow for more complicated scenarios

[Steven Hawkins (JIRA)]

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

Steven Hawkins resolved TEIID-2263.
-----------------------------------

    Resolution: Done


Implemented the view handling when the hint target starts with \@

There are a couple of corner case issues here, such as a potential conflict with hints that target tables starting with \@ and the hint can only match short names.  However neither of these seem like too great of issues.

Logic to handle subqueries and unions will need to be added at some point, but the logic (and possibly all hints handling) will need to be moved to run prior to rewriting the query as it's possible for subqueries and even union branches to to be removed at that point.  Alternatively we'd have to look at numbering or otherwise identifying query parts as part of resolving to be available for hint application.

> makedep makenotdep hints should allow for more complicated scenarios
> --------------------------------------------------------------------
>
>                 Key: TEIID-2263
>                 URL: https://issues.jboss.org/browse/TEIID-2263
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.8
>
>         Attachments: dep.patch
>
>
> In the option clause makedep and makenotdep take what are typically fully-qualified names and mark all matching tables/views in the query.  This is not generally a good idea.  We should allow for something akin to oracle global table syntax (view.)*table to drill down more specifically.  Ideally we'd also account for subqueries and set operations as well. 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)