[MDEV-12443] ST_Contains doesn't work as expected on InnoDB engine Created: 2017-04-04 Updated: 2017-05-02 Resolved: 2017-05-02 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | GIS, Storage Engine - InnoDB |
| Affects Version/s: | 10.2.4 |
| Fix Version/s: | 10.2.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | Reinis Rozitis | Assignee: | Alexey Botchkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 10.2-ga | ||
| Issue Links: |
|
||||||||||||
| Description |
|
When a table with geometry field and spatial index is converted from MyISAM to InnoDB GIS function doesn't work as expected anymore:
A small test case:
Also the oppposite funcion ST_Within works as expected. |
| Comments |
| Comment by Reinis Rozitis [ 2017-04-04 ] |
|
I havent tested this on vanilla MySQL yet / it might aswell be an upstream issue. |
| Comment by Elena Stepanova [ 2017-04-20 ] |
|
Might be the same as or closely related to |
| Comment by Alexey Botchkov [ 2017-05-02 ] |
|
That's the manifestation of the |
| Comment by Reinis Rozitis [ 2017-05-02 ] |
|
Fix version should probably be 10.2.6 as on 10.2.5 which is already released the bug still exists. |