Repository navigation
Test the nearest approach distance of a number span - #542
Merged
estebanzimanyi merged 1 commit intoOct 30, 2026
Merged
estebanzimanyi merged 1 commit into
estebanzimanyi merged 1 commit into
Conversation
test/sql/parity/036_tnumber_distance_span.test states what an intspan, bigintspan or floatspan answers through |=| and nearestApproachDistance against a tbox and against the temporal number of its base type, in either order, the cases of MobilityDB's 036_tnumber_distance with the answers its harvested output gives; a box without the value dimension raises the error MobilityDB raises, and a span of another number than the box raises the error of nad_floatspan_tbox, the typed MEOS function DuckDB reaches, where MobilityDB refuses it in its PostgreSQL wrapper, as 025_temporal_tile_tiles.test states such a case. Witness: tbox 'TBOXINT XT([0,6),[2001-01-01,2001-01-03])' |=| intspan '[10,12)' is 5.0, and intspan '[10,12)' |=| tint '[0@2001-01-01, 5@2001-01-03]' and bigintspan '[10,12)' |=| tbigint '[0@2001-01-01, 5@2001-01-03]' are 5.0; intspan '[1,2)' |=| tbox 'TBOX T([2001-01-01,2001-01-02])' raises "The tbox must have X dimension". Measured: the file holds the 10 cases of MobilityDB master's span distance section, 8 queries and 2 errors, written from its harvested 036_tnumber_distance.test.out; the generated surface at MEOS 7a0117c238 registers the 24 forms MobilityDB declares over a number span, against 18 at 7fb8e5bd65, where the span-first forms against a temporal number are absent and the tbox-first forms read their tbox argument as a span. Why: no test read a span distance, so the 6 tbox-first forms answer from the wrong operand on main and the 6 span-first forms against a temporal number stay unregistered without one failing.
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
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.
test/sql/parity/036_tnumber_distance_span.test states what an intspan, bigintspan or floatspan answers through |=| and nearestApproachDistance against a tbox and against the temporal number of its base type, in either order, the cases of MobilityDB's 036_tnumber_distance with the answers its harvested output gives; a box without the value dimension raises the error MobilityDB raises, and a span of another number than the box raises the error of nad_floatspan_tbox, the typed MEOS function DuckDB reaches, where MobilityDB refuses it in its PostgreSQL wrapper, as 025_temporal_tile_tiles.test states such a case.
Witness: tbox 'TBOXINT XT([0,6),[2001-01-01,2001-01-03])' |=| intspan '[10,12)' is 5.0, and intspan '[10,12)' |=| tint '[0@2001-01-01, 5@2001-01-03]' and bigintspan '[10,12)' |=| tbigint '[0@2001-01-01, 5@2001-01-03]' are 5.0; intspan '[1,2)' |=| tbox 'TBOX T([2001-01-01,2001-01-02])' raises "The tbox must have X dimension".
Measured: the file holds the 10 cases of MobilityDB master's span distance section, 8 queries and 2 errors, written from its harvested 036_tnumber_distance.test.out; the generated surface at MEOS 7a0117c238 registers the 24 forms MobilityDB declares over a number span, against 18 at 7fb8e5bd65, where the span-first forms against a temporal number are absent and the tbox-first forms read their tbox argument as a span.
Why: no test read a span distance, so the 6 tbox-first forms answer from the wrong operand on main and the 6 span-first forms against a temporal number stay unregistered without one failing.