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

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-5445:
----------------------------------
    Priority: Major  (was: Blocker)


TEIID-4509 introduced this change building on  TEIID-4076 and TEIID-4504.  The logic assumed that the update model count property would be set if a transaction were required.  That is the documented default behavior of execute immediate - http://teiid.github.io/teiid-documents/master/content/reference/Procedure_Language.html#_dynamic_sql_command

However I agree that in this case it leads to an odd outcome of not starting the explicitly declared transaction, so an adjustment is needed.  The workaround is to add an update clause to the execute immediate command.

> 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)