Open saig0 opened 3 years ago
The feature is partially implemented. The engine contains a range type but it is limited to function parameters or to comparison.
Currently, we can't access the properties of a range. So, we need to expose the properties and modify the parser to allow using a range in a path
expression.
More examples can be found in the TCK here.
Is your feature request related to a problem? Please describe.
Describe the solution you'd like Support ranges as new data types as described in the specs.
Related issues