-
- All Superinterfaces:
Attachable
,AutoCloseable
,DDLQuery
,DropIndexFinalStep
,Flow.Publisher<Integer>
,org.reactivestreams.Publisher<Integer>
,Query
,QueryPart
,RowCountQuery
,Serializable
,Statement
public interface DropIndexOnStep extends DropIndexFinalStep
AQuery
that can drop indexes.Referencing
XYZ*Step
types directly from client codeIt is usually not recommended to reference any
XYZ*Step
types directly from client code, or assign them to local variables. When writing dynamic SQL, creating a statement's components dynamically, and passing them to the DSL API statically is usually a better choice. See the manual's section about dynamic SQL for details: https://www.jooq.org/doc/latest/manual/sql-building/dynamic-sql.Drawbacks of referencing the
XYZ*Step
types directly:- They're operating on mutable implementations (as of jOOQ 3.x)
- They're less composable and not easy to get right when dynamic SQL gets complex
- They're less readable
- They might have binary incompatible changes between minor releases
- Author:
- Lukas Eder
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method Description DropIndexFinalStep
on(String tableName)
Specify the table expression on which to drop an index.DropIndexFinalStep
on(Name 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.-
Methods inherited from interface org.jooq.Attachable
attach, configuration, detach
-
Methods inherited from interface java.util.concurrent.Flow.Publisher
subscribe
-
Methods inherited from interface org.jooq.Query
bind, bind, cancel, close, execute, executeAsync, executeAsync, getBindValues, getParam, getParams, getSQL, getSQL, getSQL, isExecutable, keepStatement, poolable, queryTimeout
-
-
-
-
Method Detail
-
on
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CUBRID,DB2,DERBY,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MEMSQL,MYSQL,ORACLE,POSTGRES,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA}) DropIndexFinalStep on(Table<?> table)
Specify the table expression on which to drop an index.SQLDialect.MYSQL
,SQLDialect.MARIADB
, andSQLDialect.SQLSERVER
use table-scoped index names, not schema-scoped names. This means that in these databases, theON
clause is mandatory in order to unambiguously identify an index. In all other databases, theON
clause will simply be ignored for compatibility reasons.
-
on
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CUBRID,DB2,DERBY,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MEMSQL,MYSQL,ORACLE,POSTGRES,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA}) DropIndexFinalStep on(String tableName)
Specify the table expression on which to drop an index.SQLDialect.MYSQL
,SQLDialect.MARIADB
, andSQLDialect.SQLSERVER
use table-scoped index names, not schema-scoped names. This means that in these databases, theON
clause is mandatory in order to unambiguously identify an index. In all other databases, theON
clause will simply be ignored for compatibility reasons.
-
on
@Support({ACCESS,ASE,AURORA_MYSQL,AURORA_POSTGRES,CUBRID,DB2,DERBY,FIREBIRD,H2,HANA,HSQLDB,INFORMIX,INGRES,MARIADB,MEMSQL,MYSQL,ORACLE,POSTGRES,SQLDATAWAREHOUSE,SQLITE,SQLSERVER,SYBASE,TERADATA}) DropIndexFinalStep on(Name tableName)
Specify the table expression on which to drop an index.SQLDialect.MYSQL
,SQLDialect.MARIADB
, andSQLDialect.SQLSERVER
use table-scoped index names, not schema-scoped names. This means that in these databases, theON
clause is mandatory in order to unambiguously identify an index. In all other databases, theON
clause will simply be ignored for compatibility reasons.
-
-