Give each position operator its SQL names by class - #146
Merged
estebanzimanyi merged 1 commit intoSep 14, 2026
Merged
Conversation
A position operator has one SQL name per class of its operands, the class followed by the position: `<<` is setLeft, spanLeft, spansetLeft, tboxLeft, stboxLeft and tpcboxLeft, a temporal operand taking the class of its bounding box (MobilityDB#2717). The portable mapping holds the sixteen position operators in `positionFamilies`, each with its position, the stem those names and the MEOS C functions share (left_set_set, left_tspatial_tspatial). `families`, `byOperator` and `byBareName` carry the 25 operators that have one bare name. `attach_position_names` derives the names by class from the @sqlfn tags of the functions whose @sqlop is the operator, once the @sqlfn map is attached, into `portableAliases.positionNames`: 64 names for the 16 operators over MobilityDB master. A name that is not its class followed by the position, or an operator that no function carries, raises. The parity audit lists each position operator under `byPosition`, backed by the MEOS family its position prefixes and reported with its SQL names by class. The schema, the tests and the documentation cover the new section; the documentation's family table carries the spelled-out comparison names.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A position operator has one SQL name per class of its operands, the class
followed by the position:
<<is setLeft, spanLeft, spansetLeft, tboxLeft,stboxLeft and tpcboxLeft, a temporal operand taking the class of its
bounding box (MobilityDB#2717). The portable mapping holds the sixteen
position operators in
positionFamilies, each with its position, the stemthose names and the MEOS C functions share (left_set_set,
left_tspatial_tspatial).
families,byOperatorandbyBareNamecarry the25 operators that have one bare name.
attach_position_namesderives the names by class from the @sqlfn tags ofthe functions whose @sqlop is the operator, once the @sqlfn map is attached,
into
portableAliases.positionNames: 64 names for the 16 operators overMobilityDB master. A name that is not its class followed by the position,
or an operator that no function carries, raises.
The parity audit lists each position operator under
byPosition, backed bythe MEOS family its position prefixes and reported with its SQL names by
class. The schema, the tests and the documentation cover the new section;
the documentation's family table carries the spelled-out comparison names.