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
Row2 is historically special, because the SQL standard defines an OVERLAPS predicate on it. But I kinda feel that we shouldn't continue "abusing" Row2 for this purpose, but rather, introduce a new Range<T> type (possibly extending Row2<T, T>), which makes these things a bit more specific.
In PostgreSQL, this type could map to native RANGE types, too.
A predicate similar to our existing
Row2.overlaps(Row2)
predicate isRow2.contains(Row2)
, where a row is considered a range of values, e.g.:The implementation would look like this:
For the record:
The text was updated successfully, but these errors were encountered: