Spatial column types (GEOMETRY, POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION) are already supported in the Db dialects (DDL) and MySQL describeColumns. But reading a spatial column returns the raw WKB byte string - MySQL returns SRID-prefixed WKB, PostgreSQL/PostGIS returns EWKB - so findFirst() on a row with a POINT column yields unusable binary.
Add geometry value objects and hydrate spatial column values into them on model read, for MySQL and PostgreSQL.
Spatial column types (
GEOMETRY,POINT,LINESTRING,POLYGON,MULTIPOINT,MULTILINESTRING,MULTIPOLYGON,GEOMETRYCOLLECTION) are already supported in the Db dialects (DDL) and MySQLdescribeColumns. But reading a spatial column returns the raw WKB byte string - MySQL returns SRID-prefixed WKB, PostgreSQL/PostGIS returns EWKB - sofindFirst()on a row with aPOINTcolumn yields unusable binary.Add geometry value objects and hydrate spatial column values into them on model read, for MySQL and PostgreSQL.
Value objects for all eight geometry types + a shared base.
Parse MySQL WKB and PostGIS EWKB into those objects.
Hydrate on model read for spatial columns.
Refs: [NFR]: Support POINT column type in MySQL #14769, MySQL point field support missing #13670. Part of the DB feature-gap umbrella [NFR]: Support MySQL 8 #14719.