This topic has been updated for build 1823.
The OData Server complies with OData protocol version 2 specifications with some limitations and exceptions.
These considerations are not explicitly defined by OData protocol specifications.
Schema changes Restart the OData Server utility or OData Producers when you make changes to the database schema so that the changes can take effect and become visible to OData clients.
Search string filters When using OData filters—such as startswith, substringof, and indexof—on long search strings, searches are performed on the first 254 bytes only.
substringof changes The substringof(s1, s2) filter returns whether the s1 string is a substring of s2.
$orderby queries You must sort by entity properties only. Ordering by direction is supported, but sorting by expressions is not.
Proxy tables When creating entities in entity sets that are proxy tables in a database, ensure that all key properties are explicitly specified.
DefaultValue attributes The DefaultValue attribute is not exposed because it is not appropriate for all possible default values that an underlying column in the database can have.
A missing DefaultValue attribute does not imply that the default value for the property is null.
Stored procedures Stored procedures that return either multiple result sets or variable results (different data types based on invocation conditions) are not supported as service operations.
Service operations must be explicitly exposed using an OData Producer Service model file.
INOUT parameters are not supported.
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|