-
Notifications
You must be signed in to change notification settings - Fork 372
Update query-language.md #7733
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: develop
Are you sure you want to change the base?
Update query-language.md #7733
Conversation
| Operations allowed in call-chain | None allowed; typically used within another function, like a comparison (with syntactic sugar, this would appear on the right side of the comparison). The outer function or comparison dictates the operations allowed in the call-chain. | | ||
| Example | `literal(100)` <br> | | ||
| Notes | Literals can be `int`s, `float`s, `string`s, or `timestamp`s, where `timestamp`s follow ISO 8601 format. Note that in general `string` is interchangeable with all other formats, except when used in a `property` chained to an `entity`. In this case, we recommend using `timestamp` over `string` based on the datatype you're targeting. | |
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.
In this case, we recommend using
timestamp
overstring
based on the datatype you're targeting.
Shouldn't this say something like - we recommend matching the literal type against the data type of the entity property you are chaining against?
Also, should we mention support for date
literals here?
Proposed changes
Added changes based on changes we are making to the query language
Merge timing
ASAP