[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 15:31:22 EDT 2009


    [ https://jira.jboss.org/jira/browse/TEIID-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462741#action_12462741 ] 

Steven Hawkins commented on TEIID-493:
--------------------------------------

Usability in favor of correctness is always good in the short run, but deteriorates rapidly as usability features are added - all of the possible combinations of even seeming independent usability enhancements make for a mess of code, tests, and potentially unexpected results.  

I'm not arguing for modeling a salesforce query as a procedure.  You can model query and queryAll as two tables for simplicity, or since queryAll is a super set of query, you could just model the queryAll form and then put the detection of isDeleted=true in your connector to direct you to make the query call instead for performance.  In either case there's no potential for misleading results as there is with the default parameter approach.



> 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