[OASIS Issue Tracker] Created: (ODATA-366) Clarify whether server-generated properties can be omitted in POST, even if they are not nullable

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Clarify whether server-generated properties can be omitted in POST, even if they are not nullable
-------------------------------------------------------------------------------------------------

                 Key: ODATA-366
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-366
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData ATOM Format , OData JSON Format
    Affects Versions: V4.0_WD01
            Reporter: Evan Ireland


It is conventional to define primary key properties (and other properties such as "creationTime") as non-nullable.

However if properties (such as primary keys) are server-generated, the client cannot provide an appropriate initial value in POST.

The spec appears to be silent on this issue.

What should be done?

(1) Define the properties as nullable, and require the client to pass null values on POST.

(2) Define the properties as nullable, and allow the client to omit them from the payload (even for a "complete" entity) on POST.

(3) Define the properties as non-nullable, and require the client to pass junk values on POST.

(4) Define the properties as non-nullable, and allow the client to omit them from the payload (even for a "complete" entity) on POST.

It might help to understand what variations are supported (or "intended" to be supported) by OData V1-V3 in this respect, before we proceed to make a poposal for V4.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira