Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.11, 11.4, 11.8, 12.3, 13.1
Description
Hi,
I found that even if the input data of GeoJSON is invalid, it still accept it. There are two examples:
SELECT ST_ASTEXT(ST_GeomFromGeoJSON('{"type":"LineString","coordinates":[[1,2]]}')); -- LINESTRING(1 2), expect error |
SELECT ST_ASTEXT(ST_GeomFromGeoJSON('{"type":"Polygon","coordinates":[[[1,1],[2,2],[1,1]]]}')); -- POLYGON((1 1,2 2,1 1)), expect error |
Attachments
Issue Links
- relates to
-
MDEV-39981 Different order of JSON items causes different results
-
- In Progress
-