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-555) Clarify whether or not system query options can be used more than once in a URL


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

Ralf Handl updated ODATA-555:
-----------------------------

    Environment: [Proposed]
       Proposal: 
Proposal 1: Don't allow any system query options to be used more than once

Proposal 2:
- Allow multiple $select where the resultant projection is the union of all the individual $selects.
- Allow multiple $expand where the resultant expanded relationships is the union of all the individual $expands.
- Allow multiple $filter where the resultant query is all the individual $filters composed with AND (and combined with all $searches)
- Allow multiple $search where the resultant query is the individual $searches composed with AND (and combined with all $filters)
- All other system query options cannot be used multiple times

Proposal 3:
Continuing from proposal 2, also allow $orderby, $top and $skip to be used more than once:
- $top and $skip, add the numbers together
- Allow multiple $orderby where the resultant order by is the union of all the individual $orderbys where the $orderbys that appear earlier in the URL are given higher sort priority.

Proposal 1 is certainly the simplest.  Proposal 2 and 3 allow a more flexible request URL but they do not add any functionality that cannot be accomplished with proposal 1.

  was:
Proposal 1: Don't allow any system query options to be used more than once

Proposal 2:
- Allow multiple $select where the resultant projection is the union of all the individual $selects.
- Allow multiple $expand where the resultant expanded relationships is the union of all the individual $expands.
- Allow multiple $filter where the resultant query is all the individual $filters composed with AND (as it does with $search today)
- $search remains unchanged
- All other system query options cannot be used multiple times

Proposal 3:
Continuing from proposal 2, also allow $orderby, $top and $skip to be used more than once:
- $top and $skip, add the numbers together
- Allow multiple $orderby where the resultant order by is the union of all the individual $orderbys where the $orderbys that appear earlier in the URL are given higher sort priority.

Proposal 1 is certainly the simplest.  Proposal 2 and 3 allow a more flexible request URL but they do not add any functionality that cannot be accomplished with proposal 1.


> Clarify whether or not system query options can be used more than once in a URL
> -------------------------------------------------------------------------------
>
>                 Key: ODATA-555
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-555
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol , OData URL Conventions 
>    Affects Versions: V4.0_CSD03
>         Environment: [Proposed]
>            Reporter: Matthew Borges
>             Fix For: V4.0_CS02
>
>
> The ABNF allows system query options to be used more than once (not nested in an $expand), but none of the documents restrict this or provide an explanation of what the behavior would be when the same system query option is used more than once in the same URL.

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