Conversation
|
Overall |
it should always be |
| CAP supports a set of [portable functions](../guides/databases/cap-level-dbs#portable-functions) that can be used in all expressions. The CAP compiler automatically translates these functions to database-specific native equivalents, allowing you to use the same functions across different databases, which greatly enhances portability. | ||
|
|
||
| ## ref (path expression) { #ref } | ||
| ## ref — Element References & Path Expressions { #ref } |
We can also use SQL here. The retrieval is different, but in the end it is SQL.
The first time, we use the Node.js fluent style CQL API (as compared to CQL or the CAP Java fluent style CQL API). This imho always gets confusing when we talk about "CQL", but sometimes we mean the actual language, other times we mean a fluent style API - they may support different things in different ways...... Here we explicitly use the Node.js CQL API because the actual CQL does not support The second time, we run |



You can ignore the changes to the databases guides. They should not have been in this PR/branch.