[teiid-issues] [JBoss JIRA] (TEIID-5445) Atomic block is ignored when working with execute immediate command

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-5445:
-------------------------------------

Unrelated comment to this issue, however, I have seen atomic blocks stop the execution with exception when no transaction manager is present and transactions are disabled. Wasn't sure if that was an error or expected behaviour.

> 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
>            Priority: Blocker
>
> 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)