[teiid-issues] [JBoss JIRA] (TEIID-5763) GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files

[ https://issues.jboss.org/browse/TEIID-5763?page=com.atlassian.jira.plugin... ] Christoph John edited comment on TEIID-5763 at 6/17/19 5:31 PM: ---------------------------------------------------------------- Hello Steven, great. But I do have one further question regarding the key variable. Does it always represent the key value of the table on which the last insert was done? I mean, in case I have multiple inserts in an insert trigger on different tables, is then the key variable always associated with the record on the table of the last insert? for example: CREATE FOREIGN TABLE tableA(i integer ,k integer not null auto_increment primary key); CREATE FOREIGN TABLE tableB(i integer ,k integer not null auto_increment primary key) CREATE FOREIGN TABLE tableC(i integer ,k integer not null auto_increment primary key) create view v1 (i integer, k integer not null auto_increment primary key) OPTIONS (UPDATABLE true) as select x, y from tableC; create trigger on v1 instead of insert as for each row begin atomic insert into tableA (i) values (new.i); --key.k references tableA.k? insert into tableB (i) values (new.i); --key.k references tableB.k? insert into tableC (i) values(new.i); --key.k references tableC.k? was (Author: cjohn001): Hello Steven, great. But I do have one further question regarding the key variable. Does it always represent the key value of the table on which the last insert was done? I mean, in case I have multiple inserts in an insert trigger on different tables, is then the key variable always associated with the record on the table of the last insert? for example: CREATE FOREIGN TABLE tableA(integer ,k integer not null auto_increment primary key); CREATE FOREIGN TABLE tableB(integer ,k integer not null auto_increment primary key) CREATE FOREIGN TABLE tableC(integer ,k integer not null auto_increment primary key) create view v1 (i integer, k integer not null auto_increment primary key) OPTIONS (UPDATABLE true) as select x, y from tableC; create trigger on v1 instead of insert as for each row begin atomic insert into tableA (x) values (new.i); --key.k references tableA.k? insert into tableB (x) values (new.i); --key.k references tableB.k? insert into tableC (x) values(new.i); --key.k references tableC.k? -- This message was sent by Atlassian Jira (v7.12.1#712002)