OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Updated: (ODATA-104) Consider supporting nullable complex typed properties


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

Michael Pizzo updated ODATA-104:
--------------------------------

    Proposal: 
[Proposal is to clarify in URL Conventions and [Core], as appropriate, to clarify that we have null propogation rather than null reference exception semantics.]

The same rules apply as for referencing a navigation property with target cardinality 0..1.

Example: Companies(1)/HeadquarterAddress/Street will show similar behavior if modeled with a nullable property HeadquarterAddress of complex type Address or an optional navigation property HeadquarterAddress targeting an Address entity with some artificial key.

  was:
The current prose text does not specify any restrictions on the Nullable property facet, so the current text already implicitly allows complex properties to be null.

The same rules apply as for referencing a navigation property with target cardinality 0..1.

Example: Companies(1)/HeadquarterAddress/Street will show similar behavior if modeled with a nullable property HeadquarterAddress of complex type Address or an optional navigation property HeadquarterAddress targeting an Address entity with some artificial key.


> Consider supporting nullable complex typed properties
> -----------------------------------------------------
>
>                 Key: ODATA-104
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-104
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Priority: Minor
>             Fix For: WD01
>
>
> Today a property that is a complex type must be non-nullable. It would be nice to relax that restriction, particularly when using complex types to represent a vocabulary schema. We need to specify logic for referencing a property of a complex type whose value is null (i.e., in select, filter, etc.) without introducing null reference exceptions.

-- 
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]