[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... ] Steven Hawkins commented on TEIID-5763: --------------------------------------- An odata exception such as "{"error":{"code":null,"message":"TEIID16016 Insert into QuicklyAddedProducts success, but failed to retrieve auto generated keys from source, thus failed to show result entity; Supply the key values."}}" is what I was mentioning as issue 3. It requires that the key value is explicitly set: CREATE TRIGGER ON QuicklyAddedProducts INSTEAD OF INSERT AS FOR EACH ROW BEGIN ATOMIC DECLARE long vIdProduct; INSERT INTO Products(fkDatabaseKey) VALUES (2); vIdProduct = generated_key();--CONVERT(GENERATED_KEY('idProduct'),long); -- create a new record for the quickly added product INSERT INTO QuicklyAddedProducts_SRC(fkProduct, fkProfile, product_name, energy_100g, carbohydrates_100g, proteins_100g, fat_100g) VALUES (vIdProduct, new.fkProfile, new.product_name, new.energy_100g, new.carbohydrates_100g, new.proteins_100g, new.fat_100g); *key.fkProduct = vIdProduct;* END; And unintuitively for the view auto increment column to be not null: CREATE VIEW QuicklyAddedProducts (fkProduct long *NOT NULL* AUTO_INCREMENT ... After that things seem to work fine. I'll make another commit under this issue to not require the not null on the auto_increment. -- This message was sent by Atlassian Jira (v7.12.1#712002)