DROP INDEX does not allow ON condition
Bug #926125 reported by
Christopher Ernenwein
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Akiban SQL Parser |
Triaged
|
Medium
|
Mike McMahon | ||
Bug Description
When issuing a DROP INDEX command from MySQL MTR test conversions, the following syntax is expected to work
CREATE INDEX i1 ON t8 (c1);
DROP INDEX i1 ON t8;
Drop gives an error when the ON is included
DEBUG: statement execute failed: 42000: ERROR: Encountered " "on" "ON "" at line 1, column 15.
Was expecting one of:
<EOF>
"." ...
";" ...
LINE 1: DROP INDEX i1 ON t8;
| Changed in akiban-server: | |
| assignee: | nobody → Mike McMahon (mmcm) |
| Changed in akiban-server: | |
| status: | New → Triaged |
Revision history for this message
| Nathan Williams (nwilliams) wrote | #1 |
| Changed in akiban-sql-parser: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| assignee: | nobody → Mike McMahon (mmcm) |
| Changed in akiban-server: | |
| milestone: | none → future |
| Changed in akiban-sql-parser: | |
| milestone: | none → future |
| information type: | Private → Public |
To post a comment you must log in.
The parser already supports a fully qualified index name, e.g. DROP INDEX schema.table.index, and the server handles it. Leaving as affects server so it can be confirmed if/when enhancement is done.