Skip to content

Commit f2bd16c

Browse files
authored
Update documentation on Query Engine API usage
Clarify limitations of the Query Engine API in Strapi 5.
1 parent a8ac103 commit f2bd16c

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

docusaurus/docs/snippets/consider-document-service.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,5 @@ In most cases you should not use the Query Engine API and rather use the [Docume
44
Only use the Query Engine API if you exactly know what you are doing, for instance if you want to use a lower-level API that directly interacts with unique rows of the database.
55

66
Please keep in mind that the Query Engine API is not aware of the most advanced Strapi 5 features like Draft & Publish, Internationalization, Content History, and possibly more.
7+
This also means that the Query Engine API will not be able to use `documentId` and will use `id`, which means it could lead to unattended consequences at the database level or partial or incomplete compatibility with Strapi 5 features.
78
:::

0 commit comments

Comments
 (0)