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] Commented: (ODATA-391) Add query function defined(PropertyPath) to determine whether an instance has a property of that name


    [ http://tools.oasis-open.org/issues/browse/ODATA-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33486#action_33486 ] 

Michael Pizzo commented on ODATA-391:
-------------------------------------

I would go with "isdefined" -- I think it better conveys the intent of the function.
we treat missing dynamic properties the same as nulls, and I'm concerned about implying a difference in the url space that doesn't exist in other areas (serialization, data modification, etc.) so I would leave this part of the aggregation extensions (at least for now.)

> Add query function defined(PropertyPath) to determine whether an instance has a property of that name
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-391
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-391
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Extension for Data Aggregation , OData URL Conventions 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> We allow clients to add dynamic/undeclared properties to instances of open types, but we can't express filter conditions on the existence of a property of that name.
> This is also useful in the context of data aggregation to determine if a property has been "aggregated away". Here the extension will define that defined(...) returns false even for declared properties if they are not defined on an entity of the result set as an effect of groupby(), rollup(), or aggregate().

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