| Showing all 6 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 116352 | 2024-10-14 2:57 | 2025-01-06 5:30 | MySQL Server: GIS | Verified (274 days) | S3 | 8.0.31, 8.0.39, 8.4.2 | Any | Any | spatial index cause check table wrong |
| 111506 | 2023-06-21 3:46 | 2023-06-21 7:25 | MySQL Server: Documentation | Verified (755 days) | S3 | 5.7.42, 8.0.33 | Any | Any | Spatial index cardinality equals to the number of rows of the table. |
| 111479 | 2023-06-19 4:24 | 2023-06-19 11:42 | MySQL Server: Optimizer | Verified (757 days) | S3 | 5.7.42 | Any | Any | Optimizer estimated rows is always equal to 1 when using spatial index. |
| 107424 | 2022-05-30 5:45 | 2023-03-30 7:54 | MySQL Server: GIS | Verified (1141 days) | S2 | 8.0.26, 8.0.29, 8.0.32 | Linux | Any | st_intersects() returns different results with or without spatial index |
| 94560 | 2019-03-05 11:43 | 2019-03-07 4:30 | MySQL Server: GIS | Verified (2322 days) | S2 | 5.7, 8.0 | Any | Any | record comparison in spatial index non-leaf rtree node seems incorrect |
| 76384 | 2015-03-19 8:41 | 2015-03-20 13:44 | MySQL Server: GIS | Verified (3770 days) | S2 | 5.6.19, 5.6.25, 5.7.8 | Any | Any | Spatial index not used when checking return values explicitly |
| Showing all 6 (Edit, Save, CSV, Feed) |
