[Mobilitydb-dev] Successful build for MobilityDB with both PostGIS 2.5 and 3.1
Regina Obe
lr at pcorp.us
Mon Aug 30 16:17:50 PDT 2021
Great to hear. I’ll try to build against that in next couple of days and report if I have issues or if I have success.
Thanks,
Regina
From: Esteban Zimanyi [mailto:esteban.zimanyi at ulb.be]
Sent: Monday, August 30, 2021 6:03 PM
To: mobilitydb-dev at lists.osgeo.org; Vicky Vergara <vicky at georepublic.de>; Regina Obe <lr at pcorp.us>
Subject: Successful build for MobilityDB with both PostGIS 2.5 and 3.1
I finalized the build for MobilityDB that works for both PostGIS versions !
https://github.com/MobilityDB/MobilityDB/commits/towards-postgis3
In order to solve the discrepancies I "commented out" the results of some tests, while keeping their execution for testing robustness and keeping coverage values.
More precisely, since the result of the function lwgeom_hash for geographies (which is used for B-Tree comparison of temporal values) changed in PostGIS 3, I replaced the tests such as
SELECT tgeogpoint 'Point(1.5 1.5)@2000-01-01' < tgeogpoint 'Point(1.5 1.5)@2000-01-01';
by
SELECT 1 WHERE tgeogpoint 'Point(1.5 1.5)@2000-01-01' < tgeogpoint 'Point(1.5 1.5)@2000-01-01' IS NOT NULL;
Similarly, since the result of the ST_Azimuth function changed in PostGIS 3, I replaced the tests such as
SELECT round(degrees(azimuth(tgeogpoint 'Point(1.5 1.5)@2000-01-01')), 6);
by
SELECT 1 WHERE round(degrees(azimuth(tgeogpoint 'Point(1.5 1.5)@2000-01-01')), 6) IS NOT NULL;
Now we are ready to put all these new changes in the develop branch.
@Regina Obe <mailto:lr at pcorp.us> @Vicky Vergara <mailto:vicky at georepublic.de> Please tell me when to do this so I do not disrupt the work you are doing for enabling MobilityDB on other platforms.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mobilitydb-dev/attachments/20210830/de968801/attachment.html>
More information about the Mobilitydb-dev
mailing list