[
https://issues.jboss.org/browse/TEIID-3875?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3875:
---------------------------------------
So the user expectation here is that the view can't be used for
simple INSERT/UPDATE/DELETE, and that a trigger must be defined to specifically map the
tables/columns.
Yes. It needs corrected since the message is out of order. It should be:
Inherent UPDATE against VDB_Lineage.Model_Tables has the following issues: Multiple
failures occurred during validation:The updatable view query has a FROM clause that is not
a single table, pass-through processing will not be used for UPDATE/DELETE operations.,
The updatable view has no valid target for UPDATEs.
The issue here is that there can be quite a bit that prevents these updates from occurring
that is not stored/returned by later exceptions should an update be attempted. So rather
than having this information not reported, we're logging it once during VDB startup.
This is basically a soft metadata error - a view has been marked as updatable, but really
isn't. The other option would be to log at a detail level.
Many info messages upon startup that start with: TEIID31173
Inherent
---------------------------------------------------------------------
Key: TEIID-3875
URL:
https://issues.jboss.org/browse/TEIID-3875
Project: Teiid
Issue Type: Quality Risk
Components: Server
Affects Versions: 8.12.2
Reporter: Van Halbert
Assignee: Steven Hawkins
Attachments: server.log
See that attached server log that shows a page full of the following similar message:
[org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 1) TEIID31173 Inherent Multiple
failures occurred ..
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)