[JBoss JIRA] Created: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.
5:08 p.m.
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
5:20 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.
[
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
5:37 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.
[
https://jira.jboss.org/jira/browse/TEIID-493?page=com.atlassian.jira.plug...
]
John Doyle commented on TEIID-493:
----------------------------------
It might have limitations, but I think this would have use generally, not just with the SF
example. I know that many of our users who consume web services add defaulted values to
their models through virtualization because the service API is essentially a DB wrapper.
This would be a simpler way for them to do that.
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
6 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.
[
https://jira.jboss.org/jira/browse/TEIID-493?page=com.atlassian.jira.plug...
]
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
9:10 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.
[
https://jira.jboss.org/jira/browse/TEIID-493?page=com.atlassian.jira.plug...
]
John Doyle commented on TEIID-493:
----------------------------------
As I see it, the general problem is that we are trying to integrate with systems that have
very different semantics from ours. But moving to a procedural semantic is not a
solution. Our procedural semantic is woefully inadequate to communicate with all but the
most trivial "Hello World" web services. Salesforce offers a query call that
is semantically equivalent to SELECT. If we modeled that as a procedure, what would the
VDB developer do with it? He would have his work cut out for him. Where's the
metadata? Create a virtual on top of it for every object in the system so that a user
knows what objects and fields he can query? And then do the same for every object for
Update, Delete, Insert, etc.
My preference is to create integrations with these systems that have the greatest
flexibility and create the best user experience. Encapsulating the behavior of the
underlying system as completely as possible within our conceptual frame is one of my
goals, and if we have to expand our concepts slightly to accomplish that, I think it's
worth it in some cases. I'm not even arguing for this individual case, just against
correctness in favor of usability.
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
9:31 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.
[
https://jira.jboss.org/jira/browse/TEIID-493?page=com.atlassian.jira.plug...
]
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
7:17 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.
[
https://jira.jboss.org/jira/browse/TEIID-493?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-493:
--------------------------------------
Can this be closed based upon direction the salesforce connector is taking?
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
7:41 p.m.
New subject: [JBoss JIRA] Closed: (TEIID-493) Define a new modeling construct that can create a defaulted parameter.
[
https://jira.jboss.org/jira/browse/TEIID-493?page=com.atlassian.jira.plug...
]
John Doyle closed TEIID-493.
----------------------------
Resolution: Rejected
The initial case for this request has been satisfied in another manner.
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
5720
days inactive
5742
days old
7 comments
2 participants
participants (2)
-
John Doyle (JIRA) -
Steven Hawkins (JIRA)