[
https://jira.jboss.org/jira/browse/TEIID-236?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-236.
----------------------------------
Resolution: Deferred
I'm inclined to not add the procedural access pattern as a separate concern. Teiid
already appropriately checks for valid subset of procedural criteria in
RulePlanProcedures. Also from a designer perspective determining when an access pattern
is a procedural access pattern would simply involve checking the covered group to see if
it resolves to a procedure.
There is a case to be made that our normal concept of an access pattern should be the same
thing as a "procedural" access pattern. That would predictably restrict the
rows returned, work with procedural relational logic, and be valid for use with source
indexes. However that would be a breaking change and has not yet been a requested
feature.
Procedural access pattern
-------------------------
Key: TEIID-236
URL:
https://jira.jboss.org/jira/browse/TEIID-236
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Fix For: 6.3
Defect Tracker #24374: It would be good to introduce a concept of a procedural access
pattern (with designer support) that would capture the more restrictive semantics of
procedure input criteria (=, in, and is null).
--
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