[teiid-issues] [JBoss JIRA] Commented: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.
Steven Hawkins (JIRA)
jira-events at lists.jboss.org
Thu Apr 16 12:00:22 EDT 2009
[ https://jira.jboss.org/jira/browse/TEIID-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462624#action_12462624 ]
Steven Hawkins commented on TEIID-493:
--------------------------------------
The general problem here (including our web service modeling) is that we are constantly trying to view something with procedural semantics as if it were a relation. My preference would be to stop doing that as much as possible and to just use procedures or additional tables as necessary to ensure correctness.
> 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
More information about the teiid-issues
mailing list