[teiid-issues] [JBoss JIRA] (TEIID-5426) For Each processing for instead of triggers should materialize change set before processing

[Steven Hawkins (JIRA)]

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

Steven Hawkins resolved TEIID-5426.
-----------------------------------
    Fix Version/s: 11.1
                   11.0.1
                   10.3.3
       Resolution: Done


Added an intermediate temp table to fully capture the change set. 

> For Each processing for instead of triggers should materialize change set before processing
> -------------------------------------------------------------------------------------------
>
>                 Key: TEIID-5426
>                 URL: https://issues.jboss.org/browse/TEIID-5426
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 11.0
>            Reporter: Ramesh Reddy
>            Assignee: Steven Hawkins
>             Fix For: 11.1, 11.0.1, 10.3.3
>
>
> Currently when a view is defined with Inserts, Updates and Deletes with Instead of Triggers with "FOR EACH" row processing, the change set (the rows that are changing for the statement) typically is like
> {code}
> loop on (select ids from (view) where predicate) 
> begin 
>     procedure body 
> end 
> {code}
> where there is a possibility that "procedure body" will change underlying tables such that the "loop on" query results could vary during the processing. Like concurrent updates. This could be avoided by materializing the ids in #temp table before processing any of the rows.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)