[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-294) Clarifications needed for Filter System Query Option: Operators and Functions
[ http://tools.oasis-open.org/issues/browse/ODATA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evan Ireland updated ODATA-294:
-------------------------------
Description:
Some questions which may be nicely addressed by additional clarifications in the URL Conventions spec...
Logical Operators:
Q1. Apart from EQ and NE (where comparison with null can be easily understood to always return TRUE or FALSE), what is the result of using GT, GE, LT, LE with one (or both arguments) being NULL?
Possible answers: (a) undefined by the spec; (b) result is NULL; (c) result is FALSE; (d) a NULL value is considered less-than non-NULL values.
If the answer is (b) NULL, then we should define that a filter that evaluates to NULL is considered FALSE, for the purposes of determining a filter match. Since NULLs may propagate up the filter expresion tree rather quickly.
Arithmetic Operators:
Q2. What is the result of an arithmetic operator applied to one (or both) NULL operands?
Possible answers: (a) undefined by the spec; (b) NULL.
Q3. What is the ordering of numeric types for promotion when mixed types are used (e.g. if ADD is applied to Single and Decimal, what type is the result)?
Suggested answer: SByte, Int16, Int32, Int64, Decimal, Single, Double. Decimal is considered "less" than Single because Single can in nearly all implementations have a larger exponent than Decimal (so we prefer "range" over "precision" for promotion).
Q4. What is the result of a canonical function applied to one (or more) NULL parameters?
Possible answers: (a) undefined by the spec; (b) NULL; (c) depends on the function (e.g. boolean-valued functions might return FALSE).
OrderBy:
Q5. Where does NULL occur in ascending sort, and where in descending sort?
Spaces in URLs
Q6. Examples in the spec show spaces in filters. Shouldn't these be %-encoded (e.g. "%20") so they are valid in URLs?
was:
Some questions which may be nicely addressed by additional clarifications in the URL Conventions spec...
Logical Operators:
Q1. Apart from EQ and NE (where comparison with null can be easily understood to always return TRUE or FALSE), what is the result of using GT, GE, LT, LE with one (or both arguments) being NULL?
Possible answers: (a) undefined by the spec; (b) result is NULL; (c) result is FALSE; (d) a NULL value is considered less-than non-NULL values.
If the answer is (b) NULL, then we should define that a filter that evaluates to NULL is considered FALSE, for the purposes of determining a filter match. Since NULLs may propagate up the filter expresion tree rather quickly.
Arithmetic Operators:
Q2. What is the result of an arithmetic operator applied to one (or both) NULL operands?
Possible answers: (a) undefined by the spec; (b) NULL.
Q3. What is the ordering of numeric types for promotion when mixed types are used (e.g. if ADD is applied to Single and Decimal, what type is the result)?
Suggested answer: SByte, Int16, Int32, Int64, Decimal, Single, Double. Decimal is considered "less" than Single because Single can in nearly all implementations have a larger exponent than Decimal (so we prefer "range" over "precision" for promotion).
Q4. What is the result of a canonical function applied to one (or more) NULL parameters?
Possible answers: (a) undefined by the spec; (b) NULL; (c) depends on the function (e.g. boolrean-valued functions might return FALSE).
OrderBy:
Q5. Where does NULL occur in ascending sort, and where in descending sort?
Spaces in URLs
Q6. Examples in the spec show spaces in filters. Shouldn't these be %-encoded (e.g. "%20") so they are valid in URLs?
> Clarifications needed for Filter System Query Option: Operators and Functions
> -----------------------------------------------------------------------------
>
> Key: ODATA-294
> URL: http://tools.oasis-open.org/issues/browse/ODATA-294
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData URL Conventions
> Affects Versions: V4.0_WD01
> Reporter: Evan Ireland
>
> Some questions which may be nicely addressed by additional clarifications in the URL Conventions spec...
> Logical Operators:
> Q1. Apart from EQ and NE (where comparison with null can be easily understood to always return TRUE or FALSE), what is the result of using GT, GE, LT, LE with one (or both arguments) being NULL?
> Possible answers: (a) undefined by the spec; (b) result is NULL; (c) result is FALSE; (d) a NULL value is considered less-than non-NULL values.
> If the answer is (b) NULL, then we should define that a filter that evaluates to NULL is considered FALSE, for the purposes of determining a filter match. Since NULLs may propagate up the filter expresion tree rather quickly.
> Arithmetic Operators:
> Q2. What is the result of an arithmetic operator applied to one (or both) NULL operands?
> Possible answers: (a) undefined by the spec; (b) NULL.
> Q3. What is the ordering of numeric types for promotion when mixed types are used (e.g. if ADD is applied to Single and Decimal, what type is the result)?
> Suggested answer: SByte, Int16, Int32, Int64, Decimal, Single, Double. Decimal is considered "less" than Single because Single can in nearly all implementations have a larger exponent than Decimal (so we prefer "range" over "precision" for promotion).
> Q4. What is the result of a canonical function applied to one (or more) NULL parameters?
> Possible answers: (a) undefined by the spec; (b) NULL; (c) depends on the function (e.g. boolean-valued functions might return FALSE).
> OrderBy:
> Q5. Where does NULL occur in ascending sort, and where in descending sort?
> Spaces in URLs
> Q6. Examples in the spec show spaces in filters. Shouldn't these be %-encoded (e.g. "%20") so they are valid in URLs?
--
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]