• <<: Is the first numeric or range value scritly left of the second one?
• >>: Is the first numeric or range value strictly right of the second one?
• &<: Is the first numeric or range value not to the right of the second one?
• &>: Is the first numeric or range value not to the left of the second one?
• -|-: Is the first numeric or range value adjacent to the second one?
• <<#: Is the first time value scrictly before the second one?
• #>>: Is the first time value strictly after the second one?
• &<#: Is the first time value not after the second one?
• #&>: Is the first time value not before the second one?
• <<: Is the first numeric or range value scritly left of the second one? • >>: Is the first numeric or range value strictly right of the second one? • &<: Is the first numeric or range value not to the right of the second one? • &>: Is the first numeric or range value not to the left of the second one? • -|-: Is the first numeric or range value adjacent to the second one? • <<#: Is the first time value scrictly before the second one? • #>>: Is the first time value strictly after the second one? • &<#: Is the first time value not after the second one? • #&>: Is the first time value not before the second one?
Invalid operations should throw accordingly
Refer MobilityDB docs for more information: https://docs.mobilitydb.com/MobilityDB/master/ch02.html#time_relpos_operators
Todo Checklist