[OASIS Issue Tracker] (ODATA-803) Collection-valued property: Define default value for nullable facet

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

     [ https://issues.oasis-open.org/browse/ODATA-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-803:
--------------------------------

    Proposal: 
Proposal:
Absence of nullable facet on collection means it's unknown if  you can insert nulls. You can try, but it may fail.
Nullable=true means that the collection *may* contain null values (although attempting to insert a null value may still fail for a variety of reasons)
Nullable=false means that the collection can not contain null values

  was:
Define the default value for Nullable facet as true (for single-valued and) for collection-valued properties. Add note that absence of Nullable facet doesn't guarantee that service will accept null values.

Applied: https://www.oasis-open.org/committees/download.php/55611/odata-v4.0-wd08-part3-csdl-2015-05-07.docx



> Collection-valued property: Define default value for nullable facet
> -------------------------------------------------------------------
>
>                 Key: ODATA-803
>                 URL: https://issues.oasis-open.org/browse/ODATA-803
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Applied]
>            Reporter: Martin Zurmuehl
>             Fix For: V4.0_ERRATA03
>
>
> We missed to spell out the default value for the Nullable facet. For single valued properties we defined the default value as true.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)