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-264) Allow omitting parent key(s) in URLs to contained children


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

Ralf Handl updated ODATA-264:
-----------------------------

    Proposal: 
If a navigation property leading to a related entity type has a partner navigation property that specifies a referential constraint, then those key properties of the related entity that take part in the referential constraint MAY be omitted from URLs.

Example: Order contains OrderItem, key of Order is ID, key of OrderItem is OrderID and ItemNo, with a referential constraint tying the value of the OrderID key property of the OrderItem to the value of the ID property of the Order. Then the following URLs are equivalent:

~/Orders(1)/Items(OrderID=1,ItemNo=2)
~/Orders(1)/Items(2)

If the constrained key part is specified then it MUST match the parent.
If the key is included in the content it must be ignored.
This should apply any time there is a referential constraint

Accepted: https://www.oasis-open.org/committees/download.php/48481/odata-meeting-28_on-20130307-minutes.html#odata-264

  was:
If a navigation property specifes ContainsTarget="true" and the partner navigation property on the contained child type specifies a referential constraint, then child key properties that take part in the referential constraint MAY be omitted from URLs.

Example: Order contains OrderItem, key of Order is ID, key of OrderItem is OrderID and ItemNo, with a referential constraint tying the value of the OrderID key property of the OrderItem to the value of the ID property of the Order. Then the following URLs are equivalent:

~/Orders(1)/Items(OrderID=1,ItemNo=2)
~/Orders(1)/Items(2)

If the constrained key part is specified then it MUST match the parent.
If the key is included in the content it must be ignored.
This should apply any time there is a referential constraint

Accepted: https://www.oasis-open.org/committees/download.php/48481/odata-meeting-28_on-20130307-minutes.html#odata-264


> Allow omitting parent key(s) in URLs to contained children
> ----------------------------------------------------------
>
>                 Key: ODATA-264
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-264
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> Containment allows specifying 

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