-
Notifications
You must be signed in to change notification settings - Fork 142
[CDS/CXL] Edit CXL guide #2363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[CDS/CXL] Edit CXL guide #2363
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 } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.