This also prevents us from using Automated migration tools.
mysqli_query(): (22023/3037): Invalid GIS data provided to function st_astext.
When visualizing the data in wc_wpgmza of row longlat with MyPHPAdmin
This is the same table and row causing the issue.
-
This reply was modified 3 years, 1 month ago by
Michael.
Very good chance this fixes the issue. I do not see any side effects, yet.
UPDATE wc_wpgmza SET lnglat = POINT( lng, lat )
Hi @mgparisi,
Thank you for reaching out, we do appreciate your time. Our apologies for the trouble experienced.
Yes, that is correct, we make use of spatial data for our positioning storage, while a duplicate of this data is stored in the lat/lng data as well as a backup of location data in a non-spatial format, as well as backwards compatibility for older versions of the plugin.
Unfortunately, exporting this data or making use of an automated migration system may cause the export SQL to fail due to the spatial data not being set, or in some cases not being encoded as it is exported.
As such, for migration, we do recommend excluding the spatial data columns to allow the export to complete without the column.
We would also like to thank you for sharing your solution, we will definitely look into some automated steps which include this in the future.
