[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-366) Clarify whether server-generated properties can be omitted in POST, even if they are not nullable
[ http://tools.oasis-open.org/issues/browse/ODATA-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Drees updated ODATA-366: ------------------------------- Resolution: https://www.oasis-open.org/committees/download.php/49206/odata-v4.0-wd02-part1-protocol-2013-05-16.docx https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Core.V1.xml?rev=295 Accepted: https://www.oasis-open.org/committees/download.php/49557/odata-meeting-41_on-20130613_14-F2F-minutes.html#odata-366 was: https://www.oasis-open.org/committees/download.php/49206/odata-v4.0-wd02-part1-protocol-2013-05-16.docx https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/vocabularies/Org.OData.Core.V1.xml?rev=295 > 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 Protocol > Affects Versions: V4.0_CSD01 > Environment: [Applied] > Reporter: Evan Ireland > Assignee: Ralf Handl > Fix For: V4.0_CSD02 > > > 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]