Skip to content

Relational Operator -- expanding to reflect types text & binary, address cross-type comparisons (+ tweaks) #70

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Mar 2, 2023
Merged

Relational Operator -- expanding to reflect types text & binary, address cross-type comparisons (+ tweaks) #70

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
998d959
Adding rule for type text + alphabetizing + style standardizing
bgribaudo Jan 19, 2023
d630b91
Adding type binary
bgribaudo Jan 19, 2023
933c49e
Rephrasing away from type equality
bgribaudo Jan 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 13 additions & 6 deletions query-languages/m/m-spec-operators.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -619,22 +619,24 @@ The following holds when evaluating an expression containing the relational oper

* Errors raised when evaluating the `x` or `y` operand expressions are propagated.

* The values produced by evaluating both the `x` and `y` expressions must be a number, date, datetime, datetimezone, duration, logical, null or time value. Otherwise, an error with reason code `"Expression.Error"` is raised.
* The values produced by evaluating both the `x` and `y` expressions must be a binary, date, datetime, datetimezone, duration, logical, number, null, text or time value. Otherwise, an error with reason code `"Expression.Error"` is raised.

* If either or both operands are `null`, the result is the `null` value.
* Both operands must be the same kind of value or `null`. Otherwise, an error with reason code `"Expression.Error"` is raised.

* If both operands are logical, the value `true` is considered to be greater than `false`.
* If either or both operands are `null`, the result is the `null` value.

* If both operands are durations, then the values are compared according to the total number of 100-nanosecond ticks they represent.

* Two times are compared by comparing their hour parts and, if equal, their minute parts and, if equal, their second parts.
* Two binaries are compared byte by byte.

* Two dates are compared by comparing their year parts and, if equal, their month parts and, if equal, their day parts.

* Two datetimes are compared by comparing their year parts and, if equal, their month parts and, if equal, their day parts and, if equal, their hour parts and, if equal, their minute parts and, if equal, their second parts.

* Two datetimezones are compared by normalizing them to UTC by subtracting their hour/minute offset and then comparing their datetime components.

* Two durations are compared according to the total number of 100-nanosecond ticks they represent.

* Two logicals are compared such that `true` is considered to be greater than `false`.

* Two numbers `x` and `y` are compared according to the rules of the IEEE 754 standard:

* If either operand is `#nan`, the result is `false` for all relational operators.
Expand All @@ -648,6 +650,11 @@ The following holds when evaluating an expression containing the relational oper

* A `#infinity` value is considered greater than all other number values, but equal to another `#infinity`.

* Two texts are compared by using a character-by-character ordinal, case-sensitive, culture-insensitive comparison.

* Two times are compared by comparing their hour parts and, if equal, their minute parts and, if equal, their second parts.


## Conditional logical operators

The `and` and `or` operators are called the conditional logical operators.
Expand Down