| Showing 1-30 of 39 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 23568 | 2006-10-24 2:45 | 2011-02-16 23:43 | MySQL Server: GIS | Verified (6415 days) | S4 | 5.0.26 | Any | Any | "point" column makes MyISAM row_format dynamic |
| 90023 | 2018-03-12 13:51 | 2022-10-13 13:13 | MySQL Server: GIS | Verified (2256 days) | S4 | 8.0 | Any | Any | [Feature request] Shape File import/export tool |
| 45744 | 2009-06-25 11:19 | 2012-05-18 20:19 | MySQL Server: GIS | Verified | S4 | - | Any | Any | 3d GIS projection extensions needed |
| 90982 | 2018-05-23 7:45 | 2018-06-13 7:12 | MySQL Server: GIS | Verified (2165 days) | S4 | 5.6+ | Any | Any | Add ability to set SRID via MySQL-specific geometry functions |
| 96761 | 2019-09-05 3:00 | 2019-09-06 6:44 | MySQL Server: GIS | Verified (1715 days) | S4 | 8.0 | Any | Any | Add ST_GeoHex(),ST_PolygonFromGeoHex() function |
| 96760 | 2019-09-05 2:56 | 2019-09-06 6:43 | MySQL Server: GIS | Verified (1715 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 (1715 days) | S4 | 8.0 | Any | Any | Add ST_Pluscodes(),ST_PointFromPluscodes(),ST_Lat/LongFromPluscodes() function |
| 96759 | 2019-09-05 2:39 | 2019-09-06 6:51 | MySQL Server: GIS | Verified (1715 days) | S4 | 8.0 | Any | Any | Add ST_Quadkey(),ST_PointFromQuadkey(),ST_Lat/LongFromQuadkey() function |
| 113167 | 2023-11-21 14:17 | 2023-11-22 7:24 | MySQL Server: GIS | Verified (177 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 (175 days) | S3 | 8.2.0, 8.0.35 | Any | Any | After swapping the X and Y coordinates, ST_Crosses gives the incorrect answer. |
| 92868 | 2018-10-19 19:25 | 2018-11-06 6:25 | MySQL Server: GIS | Verified (2037 days) | S6 | 5.7.23, 5.7.24 | CentOS | x86 | Assertion "Geometry::is_valid_geotype(gt)" |
| 107380 | 2022-05-23 16:51 | 2023-03-30 8:05 | MySQL Server: GIS | Verified (724 days) | S4 | 8.0 | Any | Any | Contribution: Add ST_SHORTEST_DIR_PATH |
| 97221 | 2019-10-15 3:41 | 2019-10-15 5:30 | MySQL Server: GIS | Verified (1676 days) | S4 | 8.0 | Any | Any | Enabling the axis-order option even in Cartesian coordinate systems |
| 28300 | 2007-05-08 10:03 | 2011-02-16 23:43 | MySQL Server: GIS | Verified (6219 days) | S4 | any | Any | Any | General RTREE indicies |
| 96963 | 2019-09-22 14:51 | 2019-09-23 16:43 | MySQL Server: GIS | Verified (1698 days) | S3 | 8.0, 5.7.27, 8.0.17 | Any | Any | gis function incompatible between 5.6 vs 8.0 |
| 55418 | 2010-07-20 23:18 | 2011-02-16 23:44 | MySQL Server: GIS | Verified (5048 days) | S4 | 5.1.35 | Any | Any | GIS functions in 5.1.35 are not 3D |
| 107896 | 2022-07-15 13:50 | 2022-07-18 15:21 | MySQL Server: GIS | Verified (671 days) | S2 | 8.0 | Any | Any | if exchange the order of input geo, st_intersects will get opposite result |
| 93984 | 2019-01-18 21:34 | 2020-03-04 20:15 | MySQL Server: GIS | Verified (1945 days) | S4 | 8 | Any | Any | Implement Geographic Support for Remaining Spatial Functions |
| 107435 | 2022-05-31 13:06 | 2022-06-01 14:26 | MySQL Server: GIS | Verified (716 days) | S3 | Any | Any | It will return success from expr ST_GeomFromWKB with invalid wkb | |
| 101649 | 2020-11-17 16:25 | 2020-11-18 14:15 | MySQL Server: GIS | Verified (1276 days) | S4 | 8.0 | Any | Any | k-nn nearest neighbor, Order by, Calculated value, Spatial index |
| 83562 | 2016-10-27 6:12 | 2016-11-02 12:15 | MySQL Server: GIS | Verified (2753 days) | S4 | 5.7 | Any | Any | Level of precision during spatial types definition |
| 77712 | 2015-07-14 7:16 | 2021-04-26 16:16 | MySQL Server: GIS | Verified (3230 days) | S3 | 8.0.0 | Any | Any | mysql_real_query does not report an error for some queries! |
| 94560 | 2019-03-05 11:43 | 2019-03-07 4:30 | MySQL Server: GIS | Verified (1898 days) | S2 | 5.7, 8.0 | Any | Any | record comparison in spatial index non-leaf rtree node seems incorrect |
| 102599 | 2021-02-15 12:11 | 2023-12-19 10:19 | MySQL Server: GIS | Verified (1186 days) | S5 | 8.0.22 | Windows (Win 10) | x86 (NVMe RAM) | Slow performance of MySQL 8 compared with 5.7 on geographical SELECT |
| 111851 | 2023-07-22 22:59 | 2023-07-26 6:55 | MySQL Server: GIS | Verified (296 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 (3346 days) | S2 | 5.6.19, 5.6.25, 5.7.8 | Any | Any | Spatial index not used when checking return values explicitly |
| 113888 | 2024-02-04 3:38 | 2024-02-04 12:19 | MySQL Server: GIS | Verified (103 days) | S2 | 8.0 | Linux | x86 | st_contains function result is obviously wrong |
| 103678 | 2021-05-13 8:45 | 2021-05-13 16:10 | MySQL Server: GIS | Verified (1100 days) | S2 | MySQL 8.0.20, MySQL 8.0.25 | Linux | x86 | ST_Contains function returns incorrect result. |
| 92159 | 2018-08-23 13:37 | 2018-08-27 8:45 | MySQL Server: GIS | Verified (2090 days) | S1 | 5.7/8.0 | Windows | Any | st_intersects with srid 4326 unexpected values as a result |
| 107424 | 2022-05-30 5:45 | 2023-03-30 7:54 | MySQL Server: GIS | Verified (717 days) | S2 | 8.0.26, 8.0.29, 8.0.32 | Linux | Any | st_intersects() returns different results with or without spatial index |
| Showing 1-30 of 39 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
