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

Ralf Handl updated ODATA-104:
-----------------------------

    Component/s:     (was: OData Protocol v1.0)

Removed Protocol from components as the corresponding section in $filter doesn't reach that level of detail

> 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 URL Conventions v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Ralf Handl
>            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