Bug #20816 | SPATIAL KEY InnoDB crash | ||
---|---|---|---|
Submitted: | 2 Jul 2006 22:46 | Modified: | 3 Jul 2006 8:45 |
Reporter: | Ask Hansen (Basic Quality Contributor) | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.22 | OS: | Linux (Linux x86_64) |
Assigned to: | CPU Architecture: | Any |
[2 Jul 2006 22:46]
Ask Hansen
[2 Jul 2006 22:48]
Ask Hansen
In #15860 Alex said: "This bug was actually fixed as you can't create spatial index in InnoDB table anymore, so the server doesn't crash in the manner mentioned above." Hardly a fix, but even that doesn't seem to be working...
[3 Jul 2006 8:45]
Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. And as Alexey said, you can not create SPATIAL INDEX using last 5.0.23 bk sources: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 5.0.23 .... mysql> CREATE TABLE geom (g GEOMETRY not null, SPATIAL INDEX(g)) engine innodb; ERROR 1464 (HY000): The used table type doesn't support SPATIAL indexes