You probably don’t want to set this option unless you’re finding your query to be especially slow. For better performance, you can set "orderingSpecifier": "discard".
The purpose of this option is to specify how a parent view’s ORDER BYs interact with a derived view you’re querying. By default, ORDER BYs from ancestor views are inherited by derived views or ad-hoc queries as additional ordering constraints. In addition, when the page parameter is used, a total order is imposed in order to ensure that the row ordering is consistent across requests for different pages.
| Value | Is Default | Description |
|---|---|---|
| total | only if page param is present |
Impose an arbitrary total ordering consistent with the query’s declared order by, including inherited orderings. |
| no_preserve | Ignore the ancestors’ ORDER BYs when determining row order |
|
| discard | Ignore both the ancestors’ and current view’s ORDER BYs |