[teiid-issues] [JBoss JIRA] (TEIID-3952) Update to updatable internal materialized view should update the materialized view as well as the database

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-3952:
---------------------------------------

Another wrinkle in this is that we'll need to consider the current materialization status.  If the update happens when the materialization is invalid, we should probably just ignore the write through effect.  Also to do this in a straight-forward manner for internal materialization, we'll need to open up the temp table logic to access global tables for updates - not just select.

> Update to updatable internal materialized view should update the materialized view as well as the database
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-3952
>                 URL: https://issues.jboss.org/browse/TEIID-3952
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: VDB
>    Affects Versions: 8.7
>         Environment: Red Hat JBoss Data Virtualization 6.2 based on Teiid 8.7.x
>            Reporter: Andy Yuen
>            Assignee: Steven Hawkins
>              Labels: jboss
>             Fix For: 9.2
>
>
> Updating an updatable internal materized view updates the database but not the materialized view at present. The requested enhancement is that they, both, should be updated.
> Setup
> Client - SquirrelSQL to access JDV
> JDV 6.2 - with an updatable nternal materialized view of one table from the data source
> Data Source - just one data source: MySQL
> I can see from the console that the target table/view has been materialized
> Then I did the following:
> 1) select a row from the materialized table
> 2) update a field in a row in the materialized view
> 3) select that row (value unchanged ie, same as int 1) - tried multiple times
> 4) issue EXEC SYSADMIN.refreshMatViewRow(...) using primary key for the row that has been changed
> 5) select that row (value unchanged) - now I can see the changed data
> This behaviour is counter-intuitive because I was expecting that since it is an updatable materialized view, my change will write through the materialized view ie, change both the materialized view as well as the database. But in this case, it changed the database and not the materialized view?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)