MariaDB - > MySQL Migration GEOMETRY Issue? Running 2.6.4

[WorksAtAUni]

Did anyone ever resolve the GEOMETRY bug and or migration issues from MariaDB to MySQL 8 fully? Or is this a question of somehow identifying every misaligned record fixing it, and moving

We've looked for Nulls, and they aren't there and my reading of this:
#490

I think, seems to direct us to update to the MySQL data type to POLYGON (on create table?) and figure out manually how the polygon is busted and then migrate?

And that sort of leads to this comment but not sure if the feature was implemented.
https://github.com/scholarslab/Neatline/tree/bug/mysql-functions and looking at #292 underneath (unimplemented feature) seems to tell me we have things to do but curious what others have done to make it go properly?

We are running the latest plugin that I am aware of, 2.6.4

Just feel like I missed a post or a step somewhere that would make this all go away... lol (and we have a lot of sites)

[WorksAtAUni]

Are we in the uncomfortable position of having to either delete problematic records and recreate them or somehow identifying and addressing the underlying issue ourselves and seeing if it is delete/recreate/somehow edit for each record (the NULL troubleshooting advice didn't turn anything up). MySQL supports Geometry collections as used with MariaDB (I think, pretty sure) and just wondering if there is an approach beyond getting up to speed on WKT or if there is an ETL approach that has worked for you all?

[mobleyt]

Are we in the uncomfortable position of having to either delete problematic records and recreate them or somehow identifying and addressing the underlying issue ourselves and seeing if it is delete/recreate/somehow edit for each record (the NULL troubleshooting advice didn't turn anything up). MySQL supports Geometry collections as used with MariaDB (I think, pretty sure) and just wondering if there is an approach beyond getting up to speed on WKT or if there is an ETL approach that has worked for you all?

Did you ever come to a conclusion on this? I'm in the awkward position of figuring how to migrate a legacy omeka db to MySQL 8 and having no luck.

[WorksAtAUni]

Awkward is the right word.

We were not any of the geometry migration use cases you can find searching/googling (for neatline or others), some we dug deep for (iirc correctly there were even suggestions about geometry migration on the MySQL site but it has been a while, maybe it was MariaDB).

It the end, we deleted the (thankfully few) problematic records so it could migrate cleanly. We did not note any weird side effects (maybe there aren't any, maybe we just haven't noticed them.

If we had had many, I imagine we would have dug into the plugins format, Polygons and WKT/WKB more deeply to see how to convert the Maria format to something MySQL would ingest. Another gocha was the PK size from Maria to MySQL IIRC (but we just edited the create table code)

Really, I think I would have preferred to stick with MariaDB but it was an infrastructure change forced on us by our CPanel vendor.