diff --git a/docs/odata-url-conventions/odata-url-conventions.html b/docs/odata-url-conventions/odata-url-conventions.html index 19b7c28e..11d6aefd 100644 --- a/docs/odata-url-conventions/odata-url-conventions.html +++ b/docs/odata-url-conventions/odata-url-conventions.html @@ -1025,7 +1025,7 @@

OData-ABNF commonExpr syntax rule defines the formal grammar of common expressions.

-

The following subsections specify situations in which expressions evaluate to null if operands or parameters do not have the types expected by an operator or function. Notwithstanding these rules, if such a type discrepancy can be inferred for an expression that appears in a request, services SHOULD reject the request with an error message explaining the discrepancy. The inferral could be based on, for example, the declared type of a property or the type of a literal value that occurs in the expression.

+

The following subsections specify situations in which expressions evaluate to null if operands or parameters do not have the types expected by an operator or function. Notwithstanding these rules, if such a type discrepancy can be inferred for an expression that appears in a request independently of the underlying data, services SHOULD reject the request with an error message explaining the discrepancy. The inferral could be based on, for example, the declared type of a property or the type of a literal value that occurs in the expression.

Example 51: In a search for people above a certain age

http://host/service/People?$filter=Age gt '50'
diff --git a/docs/odata-url-conventions/odata-url-conventions.md b/docs/odata-url-conventions/odata-url-conventions.md index 8df530ef..7fe87de7 100644 --- a/docs/odata-url-conventions/odata-url-conventions.md +++ b/docs/odata-url-conventions/odata-url-conventions.md @@ -1561,7 +1561,8 @@ grammar of common expressions. The following subsections specify situations in which expressions evaluate to `null` if operands or parameters do not have the types expected by an operator or function. Notwithstanding these rules, if such a type discrepancy can be inferred for an expression -that appears in a request, services SHOULD reject the request with an error message +that appears in a request independently of the underlying data, +services SHOULD reject the request with an error message explaining the discrepancy. The inferral could be based on, for example, the declared type of a property or the type of a literal value that occurs in the expression. diff --git a/odata-url-conventions/5 Query Options.md b/odata-url-conventions/5 Query Options.md index d091e227..b406e8fe 100644 --- a/odata-url-conventions/5 Query Options.md +++ b/odata-url-conventions/5 Query Options.md @@ -77,7 +77,8 @@ grammar of common expressions. The following subsections specify situations in which expressions evaluate to `null` if operands or parameters do not have the types expected by an operator or function. Notwithstanding these rules, if such a type discrepancy can be inferred for an expression -that appears in a request, services SHOULD reject the request with an error message +that appears in a request independently of the underlying data, +services SHOULD reject the request with an error message explaining the discrepancy. The inferral could be based on, for example, the declared type of a property or the type of a literal value that occurs in the expression.