You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These comparison ops (<, >, <=, >=) have different behavior than the equality ops (=, <>) in strict mode. The equality ops should never error in strict mode and never return missing in permissive mode. While the comparison ops should return an error on non-comparable types and return missing in permissive mode.
Similar to comparison ops,BETWEEN should fail type check if t1 is not comparable to t2 or t1 is not comparable to t3 (thus resulting in an error in strict mode, missing in permissive mode). Perhaps can track as separate effort to fix and add conformance tests.
jpschorr
changed the title
Comparison ops (<, >, <=, >=) should follow the spec in strict mode.
Implement Strict mode errors for Comparison ops (<, >, <=, >=) and BETWEENAug 2, 2023
Tasks:
BETWEEN
in strict modeBETWEEN
#506Originally posted by @alancai98 in #413 (comment)
Originally posted by @alancai98 in #413 (comment)
The text was updated successfully, but these errors were encountered: