[ https://issues.jboss.org/browse/TEIID-5763?page=com.atlassian.jira.plugin... ] Christoph John edited comment on TEIID-5763 at 6/23/19 7:24 PM: ---------------------------------------------------------------- Hello Steven, I have one more note regarding the removal of the NOT NULL constraint on the autoincrement key, as I just added a further Jira issue to a similar topic. I have not found the time to simply test the current sources out, as I am already on my way to holiday. I was wondering, in case I do not sent a dummy primary key, if I than still get the autogenerated key in the response of the odata request back? I am not sure what the standard specifies in this context, but I would expect that I always need to have the generated key on the client side to refer back to the created item. Here the standard says the response shall include the created entity.Even though it does not explicitely state that each attribute needs to be included, I think it would make sense. http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-pr... My thinking is that this unintuitive NOT NULL on the autogenerated key, like it was implemented in the past might derive from such a constraint. was (Author: cjohn001): Hello Steven, I have one more note regarding the removal of the NOT NULL constraint on the autoincrement key, as I just added a further Jira issue to a similar topic. I have not found the time to simply test the current sources out, as I am already on my way to holiday. I was wondering, in case I do not sent a dummy primary key, if I than still get the autogenerated key in the response of the odata request back? I am not sure what the standard specifies in this context, but I would expect that I always need to have the generated key on the client side to refer back to the created item. My thinking is that this unintuitive NOT NULL on the autogenerated key like it was in the past might derive from such a constraint. -- This message was sent by Atlassian Jira (v7.12.1#712002)