jackjoe / myxql Goto Github PK

So in general, decoding works, when testing on a single element. It does not, however, work with a fully filled up row. This is mostly seen in our actual client app, where all the sudden, when there is a Point or a Polygon, another field (for now, a :naive_datetime field) cannot be decoded.

My hunch is that bytes go missing when reading them in the polygon decoding step, which screws it up for the remaining fields. But that is just a hunch. I will try to get a failing test up with this behaviour, so we can move from there.

So we are trying to implement different geometry types into myxql. We do not have extensive postgis knowledge, we were using Mariaex for quite a while and then suddenly needed MultiPolygon, which was not included.

After many, many hours to try and get our head around the binary pattern of the internal MySQL geo format, and using external libs (Geo mix package) we finally had a small breakthrough in parsing a single point without errors!

Next up are all other types, for us, in the following order of importance:

• Point (more tests?)
• Polygon
• MultiPolygon

Then for completeness:

• LineString
• Geometry
• ...

The first thing for the polygon we need to figure out is where the number of rings/points inside the polygon is stored. For that I think we can look into Mariaex which has support for Polygons. Then, hopefully, the bridge to MultiPolygon will not be too difficult.

Let us know what bit you would like to work on, so we do not overlap.