[
https://issues.jboss.org/browse/TEIID-5445?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5445:
---------------------------------------
Wasn't sure if that was an error or expected behaviour.
If it's an appropriate exception that seems ok - you'd expect an exception as well
if you tried to explicitly start a local transaction.
Atomic block is ignored when working with execute immediate command
-------------------------------------------------------------------
Key: TEIID-5445
URL:
https://issues.jboss.org/browse/TEIID-5445
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 10.2
Environment: teiid-10.2.0 on WildFly Full 11.0.0.Final (WildFly Core
3.0.8.Final)
Reporter: dalex dalex
Assignee: Steven Hawkins
When calling in atomic block a proc which is throwing an exception after updating some
rows these changed rows won't be rolled back. That is running the following query:
{code:sql}
begin atomic
call test_upd.upd();
end ;;
{code}
all changes done in the test_upd.upd virtual procedure won't be rolled back in case
of a thrown exception there. If I'm not mistaken such behavior was introduced in scope
of TEIID-4504 issue (after introducing the Program.instructionsRequireTransaction method).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)