[
https://issues.jboss.org/browse/TEIIDDES-3010?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-3010:
----------------------------------------
After today's discussions, we have an option to attach the after-trigger SQL/DDL
properties to either the source table or the view table. The desire is to be able to
provide SQL validation as part of the UI feature as well as track dependencies (model
imports). This can most effectively be done using a the virtual metamodel.
High-level event handling
-------------------------
Key: TEIIDDES-3010
URL:
https://issues.jboss.org/browse/TEIIDDES-3010
Project: Teiid Designer
Issue Type: Enhancement
Reporter: Steven Hawkins
Assignee: Barry LaFond
Priority: Blocker
Fix For: 12.0
TEIID-4627 adds support for source level triggers to be called after CDC events.
The triggers are similar to what is supported by views, but "INSTEAD OF" is not
supported - just AFTER.
CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement
Just like view triggers new/old/changing values can be referenced. Note that unlike view
triggers, these must be named as an arbitrary number of them are supported per table (like
other of our constructs they are scoped to the table, not to the schema).
We may eventually want to support multiple event types for a single trigger and may need
to support internal events as well.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)