public interface DropIndexOnStep extends DropIndexFinalStep
Query
that can drop indexes.Modifier and Type | Method and Description |
---|---|
DropIndexFinalStep |
on(Name tableName)
Specify the table expression on which to drop an index.
|
DropIndexFinalStep |
on(java.lang.String tableName)
Specify the table expression on which to drop an index.
|
DropIndexFinalStep |
on(Table<?> table)
Specify the table expression on which to drop an index.
|
bind, bind, cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, queryTimeout
attach, configuration, detach
@Support(value={ACCESS,ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,SYBASE}) DropIndexFinalStep on(Table<?> table)
SQLDialect.MYSQL
, SQLDialect.MARIADB
, and
SQLDialect.SQLSERVER
use table-scoped index names, not
schema-scoped names. This means that in these databases, the
ON
clause is mandatory in order to unambiguously identify an
index. In all other databases, the ON
clause will simply be
ignored for compatibility reasons.
@Support(value={ACCESS,ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,SYBASE}) DropIndexFinalStep on(java.lang.String tableName)
SQLDialect.MYSQL
, SQLDialect.MARIADB
, and
SQLDialect.SQLSERVER
use table-scoped index names, not
schema-scoped names. This means that in these databases, the
ON
clause is mandatory in order to unambiguously identify an
index. In all other databases, the ON
clause will simply be
ignored for compatibility reasons.
@Support(value={ACCESS,ASE,CUBRID,DB2,DERBY,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,SYBASE}) DropIndexFinalStep on(Name tableName)
SQLDialect.MYSQL
, SQLDialect.MARIADB
, and
SQLDialect.SQLSERVER
use table-scoped index names, not
schema-scoped names. This means that in these databases, the
ON
clause is mandatory in order to unambiguously identify an
index. In all other databases, the ON
clause will simply be
ignored for compatibility reasons.
Copyright © 2018. All Rights Reserved.