[
https://issues.jboss.org/browse/TEIID-5072?page=com.atlassian.jira.plugin...
]
Steven Hawkins edited comment on TEIID-5072 at 9/21/17 11:03 AM:
-----------------------------------------------------------------
Since you are saying the inherent case, how about the explicit
trigger but single insert statement case?
That would still be built upon assumption unless we can do the appropriate analysis on the
view definition. It also would require path analysis when branching statements are used.
It's a lot of work for a corner case - and there's not a great way to convey to
the user that the scenario won't work.
was (Author: shawkins):
Since you are saying the inherent case, how about the explicit
trigger but single insert statement case?
That would still be built upon assumption unless we can do the appropriate analysis on the
view definition. It also would require path analysis when branching statements are used.
It's a lot of work for a corner case.
Generated keys should be passed from triggers
---------------------------------------------
Key: TEIID-5072
URL:
https://issues.jboss.org/browse/TEIID-5072
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.0
In the context of an update trigger we should be able to convey the generated keys to the
caller. In the case where only a single insert occurs, this should be automatic.
Otherwise we'll need functions/variables to get/set the generated keys in the
procedure. For example see the LAST_INSERT_ID function on mysql.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)