[teiid-issues] [JBoss JIRA] (TEIID-5782) When overwriting an Insert trigger with custom logic in a ddl file, the primary key is not correctly transferred back in the response of the odata layer with a dummy insert value

[Christoph John (Jira)]

    [ https://issues.jboss.org/browse/TEIID-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750864#comment-13750864 ] 

Christoph John commented on TEIID-5782:
---------------------------------------

Hello Steven, ok,
let us stay in this issue than :) I am not relying on sending of a value for autoincrement. This is of no use for me. But this was the requirement given by Teiid so far to be able to get a create accepted. The only requirement that I have is, that in case of a create request I need to get the newly created object back in the response message with the autocreated value for the primary key. 
This currently does not work for INSTEAD OF INSERT trigger.

I have not had a chance yet to check the Teiid behavior with your latest patch  which removed the NOT NULL requirement from a primary key which is AUTOINCREMENT. 
Can I expect to get the correct value in the response with this patch? I can try  this out not before mid of next week when I am back from holiday.

> When overwriting an Insert trigger with custom logic in a ddl file, the primary key is not correctly transferred back in the response of the odata layer with a dummy insert value
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-5782
>                 URL: https://issues.jboss.org/browse/TEIID-5782
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: OData
>    Affects Versions: 12.3
>            Reporter: Christoph John
>            Assignee: Steven Hawkins
>            Priority: Major
>
> Hello,
> in the past we had an issue in the odata layer, that the generated primary key of an autoincrement key was not corretly transfered back in the odata response. This issue was fixed.
> However, the current issues derives from the discussion in
> https://issues.jboss.org/browse/TEIID-5763
> where we havewritten an INSTEAD OF INSERT trigger. According to my last comment to https://issues.jboss.org/browse/TEIID-5763, there are two situations which can arrise. I have to set the 1. key group explicitely or 2. it is set implicitely.
> Now in both situations I observe the same result. When I POST an INSERT with a dummy primary key, say key=0 (as it was NOT NULL in the past, and I am still using the old sources) I retrieve key=0 in the odata response. Correct would be to get a response with the generated key instead.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)