Showing 1–30 of 34
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 76384 | 2015-03-19 8:41 | 2015-03-20 13:44 | MySQL Server: GIS | Verified (4247 days) | S2 | 5.6.19, 5.6.25, 5.7.8 | Any | Any | Spatial index not used when checking return values explicitly |
| 77712 | 2015-07-14 7:16 | 2021-04-26 16:16 | MySQL Server: GIS | Verified (4131 days) | S3 | 8.0.0 | Any | Any | mysql_real_query does not report an error for some queries! |
| 92159 | 2018-08-23 13:37 | 2018-08-27 8:45 | MySQL Server: GIS | Verified (2991 days) | S1 | 5.7/8.0 | Windows | Any | st_intersects with srid 4326 unexpected values as a result |
| 92349 | 2018-09-10 9:22 | 2020-04-17 20:57 | MySQL Server: GIS | Verified (2962 days) | S2 | 8.0.12 | Any | Any | Storage Format is wrong regarding POINT data with SRID=2443-2461,6669-6687,30161 |
| 92937 | 2018-10-24 21:08 | 2018-10-24 22:24 | MySQL Server: GIS | Verified (2933 days) | S2 | 5.7 | Linux | Any | st_isvalid returns invalid for a valid geometry. |
| 94560 | 2019-03-05 11:43 | 2019-03-07 4:30 | MySQL Server: GIS | Verified (2799 days) | S2 | 5.7, 8.0 | Any | Any | record comparison in spatial index non-leaf rtree node seems incorrect |
| 96963 | 2019-09-22 14:51 | 2019-09-23 16:43 | MySQL Server: GIS | Verified (2599 days) | S3 | 8.0, 5.7.27, 8.0.17 | Any | Any | gis function incompatible between 5.6 vs 8.0 |
| 102599 | 2021-02-15 12:11 | 2025-10-05 20:45 | MySQL Server: GIS | Verified (2087 days) | S5 | 8.0.22 | Windows (Win 10) | x86 (NVMe RAM) | Slow performance of MySQL 8 compared with 5.7 on geographical SELECT |
| 103678 | 2021-05-13 8:45 | 2021-05-13 16:10 | MySQL Server: GIS | Verified (2001 days) | S2 | MySQL 8.0.20, MySQL 8.0.25 | Linux | x86 | ST_Contains function returns incorrect result. |
| 104823 | 2021-09-03 17:49 | 2021-09-06 9:12 | MySQL Server: GIS | Verified (1885 days) | S3 | 8.0.13, 8.0.23, 8.0.26 | Any | Any | ST_Overlaps, ST_Touches returning different values in between SRID 0 and 4326 |
| 107402 | 2022-05-26 8:53 | 2022-05-31 14:24 | MySQL Server: GIS | Verified (1618 days) | S3 | 8.0 | Any | Any | value has changed when 1e-16 is input of GIS expr |
| 107424 | 2022-05-30 5:45 | 2023-03-30 7:54 | MySQL Server: GIS | Verified (1618 days) | S2 | 8.0.26, 8.0.29, 8.0.32 | Linux | Any | st_intersects() returns different results with or without spatial index |
| 107435 | 2022-05-31 13:06 | 2022-06-01 14:26 | MySQL Server: GIS | Verified (1617 days) | S3 | Any | Any | It will return success from expr ST_GeomFromWKB with invalid wkb | |
| 107896 | 2022-07-15 13:50 | 2022-07-18 15:21 | MySQL Server: GIS | Verified (1572 days) | S2 | 8.0 | Any | Any | if exchange the order of input geo, st_intersects will get opposite result |
| 111851 | 2023-07-22 22:59 | 2023-07-26 6:55 | MySQL Server: GIS | Verified (1197 days) | S2 | 8.0.32, 8.0.34, 5.7.43 | Any (Linux & Mac) | Any (x86 & ARM) | Spatial index not used for join when field is used in MBRIntersects call |
| 113167 | 2023-11-21 14:17 | 2023-11-22 7:24 | MySQL Server: GIS | Verified (1078 days) | S2 | 8.2.0, 8.0.35 | Any | Any | After creating the spatial index, ST_Disjoint gives the incorrect answer |
| 113205 | 2023-11-24 3:06 | 2023-11-24 6:01 | MySQL Server: GIS | Verified (1076 days) | S3 | 8.2.0, 8.0.35 | Any | Any | After swapping the X and Y coordinates, ST_Crosses gives the incorrect answer. |
| 113888 | 2024-02-04 3:38 | 2025-02-01 11:58 | MySQL Server: GIS | Verified (1004 days) | S2 | 8.0 | Linux | x86 | st_contains function result is obviously wrong |
| 114291 | 2024-03-10 7:20 | 2024-06-27 10:05 | MySQL Server: GIS | Verified (969 days) | S3 | 8.2.0, 8.0.36 | Any | Any | ST_Overlap gives an incorrect answer. |
| 116352 | 2024-10-14 2:57 | 2025-01-06 5:30 | MySQL Server: GIS | Verified (751 days) | S3 | 8.0.31, 8.0.39, 8.4.2 | Any | Any | spatial index cause check table wrong |
| 117036 | 2024-12-23 7:28 | 2024-12-31 5:43 | MySQL Server: GIS | Verified (681 days) | S2 | 8.0, 8.0.40 | Any | Any | Spatial Index causes CHECK TABLE to fail |
| 117042 | 2024-12-25 6:56 | 2024-12-30 13:43 | MySQL Server: GIS | Verified (674 days) | S2 | 8.0.40 | Windows | Any | ST_Within gives unexpected result with Linestring and Polygon in WGS84. |
| 117046 | 2024-12-25 12:44 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (674 days) | S2 | 8.0.40 | Any | Any | Negative buffer of a polygon gives an result that not small enough. |
| 117047 | 2024-12-26 8:27 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (674 days) | S1 | 8.0.40 | Any | Any | ST_Touches always return null with Point and GeometryCollection with Points |
| 117048 | 2024-12-26 9:06 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (674 days) | S2 | 8.0.40 | Any | Any | ST_Buffer gives unexpected reuslt using end_flat strategy with closed Linestring |
| 117063 | 2024-12-28 13:40 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (674 days) | S1 | 8.0.40 | Any | Any | Spatial index causes the disjoint predicate gives wrong result with WHERE,INNER JOIN and CROSS JOIN, |
| 117076 | 2024-12-30 13:38 | 2024-12-30 13:49 | MySQL Server: GIS | Verified (674 days) | S2 | 8.0.40 | Any | Any | ST_Intersection returns a non-empty result for two geometries that are disjoint. |
| 117120 | 2025-01-07 12:40 | 2025-01-07 12:46 | MySQL Server: GIS | Verified (666 days) | S3 | 9.0, 8.0.40 | Any | Any | Inconsistent Results with ST_Collect in WHERE Clause |
| 117129 | 2025-01-08 6:33 | 2025-01-08 7:15 | MySQL Server: GIS | Verified (665 days) | S3 | 8.0.40 | Any | Any | Potential bug in ST_Crosses |
| 117134 | 2025-01-08 10:25 | 2025-01-08 10:47 | MySQL Server: GIS | Verified (665 days) | S1 | 8.0.40 | Any | Any | ST_Buffer gives unexpected result with LinearRing |
Showing 1–30 of 34
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.016 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.