This has been a formatter issue since the syntax was introduced. I’m just on a roll today and I’m manually plugging through 50+ of these. I’m deathly afraid to touch the parser rules without explicit guidance. It generates the error message listed below on each ALTER statement with the DROP INDEX clause. It also fails to remove the extra padding after the DROP. These all come from Toad generated DDL in sync scripts and also in table rebuilds. 11.6 puts 4 spaces between DROP and INDEX with every format call. 12.1 doesn’t add the additional spaces, but generates the error and doesn’t de-space. Is there a way to kill the error messages? Does the formatter have to be changed or is there some configuration setting somewhere that would format the statements? Earlier versions stopped formatting at first sight of this syntax. At least now the other statements are formatted.
ALTER TABLE nwps.keyops DROP CONSTRAINT keyops_uk DROP INDEX;
CREATE UNIQUE INDEX nwps.keyops_uk
ON nwps.keyops (joborder_cd, coars_said, keyop_cd)
ALTER TABLE nwps.keyops ADD (
UNIQUE (joborder_cd, coars_said, keyop_cd)
USING INDEX nwps.keyops_uk
[Error] Syntax check (1: 64): ERROR line 1, col 64, ending_line 1, ending_col 68, Found ‘INDEX’, Expecting: ( COLUMN COLUMNS CONSTRAINT CONSTRAINTS PRIMARY SUPPLEMENTAL UNIQUE UNUSED