Skip to content

Place the ever and always forms of a member in its class - #278

Merged
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:om/ever-always-of-a-class-prefix
Nov 19, 2026
Merged

estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:om/ever-always-of-a-class-prefix

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

MEOS writes the ever or always form of a member with its letter before the class token (eraster_value, the ever form of raster_value), and the object model assigns a function to a class by its prefix, so e and a matched no class and those functions belonged to none. #_candidates pairs each class prefix with its ever and always forms, and #_ever_always_ooname names such a member with its letter before the name of the plain form: Raster.eValue and Raster.aValue beside Raster.value, atValue and minusValue.

Witness: test_the_ever_and_always_forms_of_a_member_stand_beside_it classifies eraster_value and araster_tile_value into Raster as eValue and aTileValue beside raster_value's value; it fails without the change.

Measured: over the catalog derived from MobilityDB master 1f59b32c28 the object model of this branch and of master differ in twelve members alone, the ever and always forms of value, valueGdal, valueSeries, tileValue, tileValueArray and tileValueSeries joining Raster; every other key of the catalog is equal; the suite passes, 701 passed and 31 skipped.

Why: the owner placed the five readers of a raster along a trajectory in one class, the letter of ever and always on the method name (2026-11-19, option A of the raster plan, MobilityDB #3775), and a binding projecting the object model then carries eRasterValue and aRasterValue.

estebanzimanyi added a commit that referenced this pull request Nov 19, 2026
MobilityDB supports one H3 release, H3_REQUIRED_VERSION of its top-level CMakeLists.txt, and its configure refuses any other; its .github/scripts/install-h3.sh builds that release from its tag. provision-meos installed libh3-dev, whichever release the PostgreSQL archive carries (4.5.0), so every libmeos build of the action stops at configure since MobilityDB pinned 4.6.0. The action takes H3 from the checkout's own script when the checkout carries it: it builds the release into a prefix cached by its version and installs it under /usr/local, where MobilityDB's CMake and the catalog parse find it, as GDAL is; a checkout predating the script takes the package as before.

Witness: the tests job of MEOS-API #278 stops at "MobilityDB requires H3 4.6.0, but the header found at /usr/include/h3/h3api.h is H3 4.5.0" (run 44578447526), after installing libh3-1 4.5.0-1.pgdg26.04+1.

Why: every consumer of provision-meos builds libmeos through it, MEOS-API's tests, GoMEOS, MobilityDuck's refresh and the JVM bindings among them.
MEOS writes the ever or always form of a member with its letter before the class token (eraster_value, the ever form of raster_value), and the object model assigns a function to a class by its prefix, so e<prefix> and a<prefix> matched no class and those functions belonged to none. #_candidates pairs each class prefix with its ever and always forms, and #_ever_always_ooname names such a member with its letter before the name of the plain form: Raster.eValue and Raster.aValue beside Raster.value, atValue and minusValue.

Witness: test_the_ever_and_always_forms_of_a_member_stand_beside_it classifies eraster_value and araster_tile_value into Raster as eValue and aTileValue beside raster_value's value; it fails without the change.

Measured: over the catalog derived from MobilityDB master 1f59b32c28 the object model of this branch and of master differ in twelve members alone, the ever and always forms of value, valueGdal, valueSeries, tileValue, tileValueArray and tileValueSeries joining Raster; every other key of the catalog is equal; the suite passes, 701 passed and 31 skipped.

Why: the owner placed the five readers of a raster along a trajectory in one class, the letter of ever and always on the method name (2026-11-19, option A of the raster plan, MobilityDB #3775), and a binding projecting the object model then carries eRasterValue and aRasterValue.
@estebanzimanyi
estebanzimanyi force-pushed the om/ever-always-of-a-class-prefix branch from 39f1bd3 to 3007001 Compare November 19, 2026 17:55
@estebanzimanyi
estebanzimanyi merged commit d217366 into MobilityDB:master Nov 19, 2026
3 checks passed
@estebanzimanyi
estebanzimanyi deleted the om/ever-always-of-a-class-prefix branch November 19, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant