tabshift/payloadcms
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

docs: mention virtual fields cannot be sorted (#3107)

Browse Source
This commit is contained in:
Dan Ribbens
2023-08-01 05:10:02 -04:00
committed by GitHub
parent 4b00850e41
commit 5ef20e3440
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/queries/overview.mdx
View File

@@ -194,7 +194,7 @@ const getPosts = async () => {
## Sort ## Sort
Payload `find` queries support a `sort` parameter through all APIs. Pass the `name` of a top-level field to sort by that field in ascending order. Prefix the name of the field with a minus symbol ("-") to sort in descending order. Payload `find` queries support a `sort` parameter through all APIs. Pass the `name` of a top-level field to sort by that field in ascending order. Prefix the name of the field with a minus symbol ("-") to sort in descending order. Because sorting is handled by the database, the field you wish to sort on must be stored in the database to work; not a [virtual field](https://payloadcms.com/blog/learn-how-virtual-fields-can-help-solve-common-cms-challenges). It is recommended to enable indexing for the fields where sorting is used.
**REST example:** **REST example:**
**`https://localhost:3000/api/posts?sort=-createdAt`** **`https://localhost:3000/api/posts?sort=-createdAt`**