[teiid-issues] [JBoss JIRA] Resolved: (TEIID-1349) Better default update procedure handling

[Steven Hawkins (JIRA)]

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

Steven Hawkins resolved TEIID-1349.
-----------------------------------

    Fix Version/s: 7.3
                       (was: 8.0)
       Resolution: Done


Updated the code to handle null update procedures as defaults.  There are many simple situations that can no be handled as pass-through.  In addition we can automatically handle many join scenarios - although only 1 table may be targeted by a delete.

It would be good to add handling for OPTION CHECK, which ensures that updates will not be inconsistent with the view (such as an update that causes a row to not be visible in the view).  It would also be good to have a notion of a cascading delete in situations where related records are deleted.

> Better default update procedure handling
> ----------------------------------------
>
>                 Key: TEIID-1349
>                 URL: https://jira.jboss.org/browse/TEIID-1349
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>    Affects Versions: 7.2
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 7.3
>
>
> We are currently very restrictive in what we can automatically handle in terms of updates procedures.  Anything other than a simple non-joined select cannot have a default update procedure.  We should look at expanding our default handling to simple joins and union all - along with designer warnings for derived columns or other situations that would not be automatically updatable. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira