[
https://issues.jboss.org/browse/TEIID-5729?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5729.
-----------------------------------
Resolution: Done
The problem here is actually that the auto value for the update count is being treated the
same as no updates. However to get an actual value that requires fully planning the
procedure as the closest logic we have comes from the requires transaction logic on the
plan. That is quite involved, so the initial fix is just to be safe and map instead to an
action. The docs have been updated to say that an explicit updatecount of 0 is expected
to map to a function.
Introduce mechanism or option to allow for mapping of side effect
free Teiid procedures to ODATA functions, and actions if procedure has side effects
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-5729
URL:
https://issues.jboss.org/browse/TEIID-5729
Project: Teiid
Issue Type: Enhancement
Components: OData
Reporter: Christoph John
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.3
This is a follow up regarding
https://issues.jboss.org/browse/TEIID-5725
As discussed there, Teiid currently does not map virtual procedures and functions to
odata functions and procedures according to the notion of "side effect free"
Please introduce a mechanism to allow for a mapping according to adequate odata
semantics.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)