| Showing 1-30 of 39 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 92159 | 2018-08-23 13:37 | 2018-08-27 8:45 | MySQL Server: GIS | Verified (2061 days) | S1 | 5.7/8.0 | Windows | Any | st_intersects with srid 4326 unexpected values as a result |
| 103678 | 2021-05-13 8:45 | 2021-05-13 16:10 | MySQL Server: GIS | Verified (1071 days) | S2 | MySQL 8.0.20, MySQL 8.0.25 | Linux | x86 | ST_Contains function returns incorrect result. |
| 113888 | 2024-02-04 3:38 | 2024-02-04 12:19 | MySQL Server: GIS | Verified (74 days) | S2 | 8.0 | Linux | x86 | st_contains function result is obviously wrong |
| 113167 | 2023-11-21 14:17 | 2023-11-22 7:24 | MySQL Server: GIS | Verified (148 days) | S2 | 8.2.0, 8.0.35 | Any | Any | After creating the spatial index, ST_Disjoint gives the incorrect answer |
| 111851 | 2023-07-22 22:59 | 2023-07-26 6:55 | MySQL Server: GIS | Verified (267 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 |
| 76384 | 2015-03-19 8:41 | 2015-03-20 13:44 | MySQL Server: GIS | Verified (3317 days) | S2 | 5.6.19, 5.6.25, 5.7.8 | Any | Any | Spatial index not used when checking return values explicitly |
| 94560 | 2019-03-05 11:43 | 2019-03-07 4:30 | MySQL Server: GIS | Verified (1869 days) | S2 | 5.7, 8.0 | Any | Any | record comparison in spatial index non-leaf rtree node seems incorrect |
| 92937 | 2018-10-24 21:08 | 2018-10-24 22:24 | MySQL Server: GIS | Verified (2003 days) | S2 | 5.7 | Linux | Any | st_isvalid returns invalid for a valid geometry. |
| 107896 | 2022-07-15 13:50 | 2022-07-18 15:21 | MySQL Server: GIS | Verified (642 days) | S2 | 8.0 | Any | Any | if exchange the order of input geo, st_intersects will get opposite result |
| 107424 | 2022-05-30 5:45 | 2023-03-30 7:54 | MySQL Server: GIS | Verified (688 days) | S2 | 8.0.26, 8.0.29, 8.0.32 | Linux | Any | st_intersects() returns different results with or without spatial index |
| 92349 | 2018-09-10 9:22 | 2020-04-17 20:57 | MySQL Server: GIS | Verified (2032 days) | S2 | 8.0.12 | Any | Any | Storage Format is wrong regarding POINT data with SRID=2443-2461,6669-6687,30161 |
| 96963 | 2019-09-22 14:51 | 2019-09-23 16:43 | MySQL Server: GIS | Verified (1669 days) | S3 | 8.0, 5.7.27, 8.0.17 | Any | Any | gis function incompatible between 5.6 vs 8.0 |
| 104823 | 2021-09-03 17:49 | 2021-09-06 9:12 | MySQL Server: GIS | Verified (955 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 (688 days) | S3 | 8.0 | Any | Any | value has changed when 1e-16 is input of GIS expr |
| 107435 | 2022-05-31 13:06 | 2022-06-01 14:26 | MySQL Server: GIS | Verified (687 days) | S3 | Any | Any | It will return success from expr ST_GeomFromWKB with invalid wkb | |
| 77712 | 2015-07-14 7:16 | 2021-04-26 16:16 | MySQL Server: GIS | Verified (3201 days) | S3 | 8.0.0 | Any | Any | mysql_real_query does not report an error for some queries! |
| 113205 | 2023-11-24 3:06 | 2023-11-24 6:01 | MySQL Server: GIS | Verified (146 days) | S3 | 8.2.0, 8.0.35 | Any | Any | After swapping the X and Y coordinates, ST_Crosses gives the incorrect answer. |
| 114291 | 2024-03-10 7:20 | 2024-03-10 7:55 | MySQL Server: GIS | Verified (39 days) | S3 | 8.2.0, 8.0.36 | Any | Any | ST_Overlap gives an incorrect answer. |
| 109666 | 2023-01-17 19:12 | 2023-02-10 12:29 | MySQL Server: GIS | Verified (456 days) | S4 | 8.0.32 | Windows | Any | ST_Transform fails when transforming from 4326 to 6350 |
| 107380 | 2022-05-23 16:51 | 2023-03-30 8:05 | MySQL Server: GIS | Verified (695 days) | S4 | 8.0 | Any | Any | Contribution: Add ST_SHORTEST_DIR_PATH |
| 101649 | 2020-11-17 16:25 | 2020-11-18 14:15 | MySQL Server: GIS | Verified (1247 days) | S4 | 8.0 | Any | Any | k-nn nearest neighbor, Order by, Calculated value, Spatial index |
| 97221 | 2019-10-15 3:41 | 2019-10-15 5:30 | MySQL Server: GIS | Verified (1647 days) | S4 | 8.0 | Any | Any | Enabling the axis-order option even in Cartesian coordinate systems |
| 96760 | 2019-09-05 2:56 | 2019-09-06 6:43 | MySQL Server: GIS | Verified (1686 days) | S4 | 8.0 | Any | Any | Add ST_LocaPoint(),ST_PointFromLocaPoint(),ST_Lat/LongFromLocaPoint() function |
| 96762 | 2019-09-05 3:04 | 2019-09-06 6:46 | MySQL Server: GIS | Verified (1686 days) | S4 | 8.0 | Any | Any | Add ST_Pluscodes(),ST_PointFromPluscodes(),ST_Lat/LongFromPluscodes() function |
| 96761 | 2019-09-05 3:00 | 2019-09-06 6:44 | MySQL Server: GIS | Verified (1686 days) | S4 | 8.0 | Any | Any | Add ST_GeoHex(),ST_PolygonFromGeoHex() function |
| 7638 | 2005-01-03 16:06 | 2022-10-13 13:18 | MySQL Server: GIS | Open | S4 | 4.1.x | Any (Any) | Any | Tool like PostGIS's SHP2SQL |
| 96759 | 2019-09-05 2:39 | 2019-09-06 6:51 | MySQL Server: GIS | Verified (1686 days) | S4 | 8.0 | Any | Any | Add ST_Quadkey(),ST_PointFromQuadkey(),ST_Lat/LongFromQuadkey() function |
| 93984 | 2019-01-18 21:34 | 2020-03-04 20:15 | MySQL Server: GIS | Verified (1916 days) | S4 | 8 | Any | Any | Implement Geographic Support for Remaining Spatial Functions |
| 90982 | 2018-05-23 7:45 | 2018-06-13 7:12 | MySQL Server: GIS | Verified (2136 days) | S4 | 5.6+ | Any | Any | Add ability to set SRID via MySQL-specific geometry functions |
| 90273 | 2018-04-02 4:41 | 2018-06-13 9:20 | MySQL Server: GIS | Verified (2136 days) | S4 | Any | Any | Well-known text POINT type with z and m |
| Showing 1-30 of 39 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
