Skip to content
Snippets Groups Projects
Verified Commit 4d15622c authored by Daniel Hornung's avatar Daniel Hornung
Browse files

DOC: update docs for new behavior of FIND queries (also for FROM)

parent ce6c7628
No related branches found
No related tags found
2 merge requests!96DOC: Added CITATION.cff to the list of files in the release guide where the...,!71F find query
Pipeline #30880 failed
......@@ -15,7 +15,7 @@ The following queries are equivalent to the former. Of course, the returned set
`FIND RECORDS ename`
You can include all entities into the results by adding the `ENTITY` keyword:
You can include all entities (Records, RecordTypes, Properties, ...) into the results by adding the `ENTITY` keyword:
`FIND ENTITY ename`.
......@@ -81,7 +81,7 @@ Examples:
`FIND ename WHICH HAS A pname1 LIKE *al1`
_Note:_ The _LIKE_ operator is will only produce expectable results with text properties.
_Note:_ The _LIKE_ operator will only produce expectable results with text properties.
#### Special Case: References
......@@ -364,7 +364,7 @@ Any result set can be filtered by logically combining POV filters or back refere
In contrast to `FIND` queries, which always return the complete entity, there are `SELECT` queries which only return the entity with only those properties which are specified in the query. The syntax is very similar to `FIND` queries - just replace the `FIND` by `SELECT <comma separated list of selectors> FROM`:
`SELECT p1, p2, p3 FROM Record ename`
`SELECT p1, p2, p3 FROM ename`
However, the `SELECT` query can also return properties of referenced entities and thereby are a means of joining entities together and return a custom view or projection:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment