Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
11.4
-
None
Description
MariaDB correctly rejects an invalid geometry but emits no warning, in contrast to MySQL. How we address this is trivial in the technical sense, but what's more interesting is whether we care to expose the parse as a warning or not, or change what the query returns.
On MariaDB:
MariaDB [test]> SELECT ST_GEOMFROMTEXT('NOTAGEOMETRY(0 0)') AS geometry_name_expected; |
+------------------------+ |
| geometry_name_expected |
|
+------------------------+ |
| NULL | |
+------------------------+ |
1 row in set (0.001 sec) |
 |
MariaDB [test]> show warnings;
|
Empty set (0.000 sec) |
On MySQL 9.6.0:
mysql> SELECT ST_GEOMFROMTEXT('NOTAGEOMETRY(0 0)') AS geometry_name_expected; |
ERROR 3037 (22023): Invalid GIS data provided to function st_geomfromtext. |
