[MDEV-17546] SPATIAL INDEX should not be allowed for FOREIGN KEY Created: 2018-10-25 Updated: 2018-10-25 Resolved: 2018-10-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.2.2, 10.3.0 |
| Fix Version/s: | 10.3.11, 10.2.19 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | gis, upstream | ||
| Issue Links: |
|
||||||||
| Description |
|
Bug#27912873 CRASH: SEGMENTATION FAULT IN HA_INNOBASE::INDEX_TYPE() blocks SPATIAL INDEX from being considered for FOREIGN KEY. No test case was included, and I was unable to come up with one that would not reject the FOREIGN KEY. That said, the function dict_foreign_qualify_index() should reject both FULLTEXT INDEX and SPATIAL INDEX, and its callers should not check for these. |