[
https://jira.jboss.org/jira/browse/TEIID-493?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-493:
--------------------------------------
We currently have no concept of an access pattern with a default value. And only
procedures invoked through named parameter syntax make use of default values. It seems
more appropriate for salesforce to expose two tables rather than implying a default
criteria value on a single unified table. The default criteria approach has a serious
drawback in determining when the appropriate criteria has not been set - for example if
the isDeleted column could be used in an non-pushdown function or predicate. In this case
you would assume that the user intended for isDeleted to be false, but that was not the
intent of the query.
Define a new modeling construct that can create a defaulted
parameter.
----------------------------------------------------------------------
Key: TEIID-493
URL:
https://jira.jboss.org/jira/browse/TEIID-493
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: John Doyle
Assignee: Steven Hawkins
Priority: Minor
I would like to be able to define on a physical model a defaulted parameter value for a
column, much like an access pattern with a default value. At runtime the default value
would be sent as a parameter if the user did not supply a value in the query.
The use case that brought this to mind is the Salesforce connector. Each Salesforce
object exposes a isDeleted column and since most uses of the connector do not want to see
deleted objects, the user will have to know that they need to have isDeleted=false in the
query. Having a 'defaulted access pattern' would allow us to encapsulate this SF
API leakage better.
--
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