3244
MySQLERRORNotableGIS / GeometryHIGH confidence
Geometry byte order is wrong endianness
Production Risk
Medium — geometry imports fail when WKB data is byte-swapped.
How to reproduce
trigger — this will error
trigger — this will error
SELECT ST_AsText(ST_GeomFromWKB(0x02010000003D0AD7A3703D0A403D0AD7A3703D2240));
expected output
ERROR 3244 (22023): Geometry byte order is wrong endianness.
Fix
Use correct byte-order flag
Use correct byte-order flag
-- Ensure WKB starts with 0x01 (little-endian) or 0x00 (big-endian) correctly.
Why this works
The first byte of WKB defines byte order; an incorrect value causes this error.
What not to do
✕
Sources
Official documentation ↗
MySQL 8.0 — 3244 ER_GIS_DATA_WRONG_ENDIANESS
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev