Uh oh!
There was an error while loading. Please reload this page.
Spatial axis order , srid migrations - #699
Conversation
* SRID fix for mariadb/mysql * Axis order updates for mysql
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (2)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
SRID fixed to 4326 for all adapters
Axis order is long-lat for all adapters
Mariadb doesn't support axis-order but mysql supports it and it is now default to long-lat
In 4326 SRID, mysql uses by default [lat, long] and ST_X will give lat as x
For geometric distances -> using srid 0 as 4326 calculates in meter
Result -> srid is fixed and we do insertion and query both in long-lat for all
Example
Long-lat insertion and fetching from mysql
Output
