[teiid-issues] [JBoss JIRA] (TEIID-2721) Resolving an aliased view prevents inherent update from working
Steven Hawkins (JIRA)
jira-events at lists.jboss.org
Fri Nov 1 07:30:02 EDT 2013
[ https://issues.jboss.org/browse/TEIID-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Hawkins resolved TEIID-2721.
-----------------------------------
Fix Version/s: 8.6
Resolution: Done
The fix is to ensure that the update validator uses the proper view symbols.
This should be rare on 8.0+ as the metadata validation will properly initialize the cached metadata, but since the entries can expire from the cache it's possible that it could occur.
> Resolving an aliased view prevents inherent update from working
> ---------------------------------------------------------------
>
> Key: TEIID-2721
> URL: https://issues.jboss.org/browse/TEIID-2721
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.6
>
> Attachments: 2721-77x.patch
>
>
> If an aliased form of an inherently updatable view is resolved first, we will cache invalid update info which prevents inherent insert/update from functioning correctly.
> For example with the view gx, first running:
> select * from gx as x
>
> will prevent an inherent insert such as:
> insert into gx (e1, e2, e3, e4) select * from pm1.g1
> from working as expected
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the teiid-issues
mailing list