-
- All Superinterfaces:
Attachable
,AttachableQueryPart
,AutoCloseable
,DDLQuery
,DropIndexCascadeStep
,DropIndexFinalStep
,Flow.Publisher<Integer>
,Publisher<Integer>
,org.reactivestreams.Publisher<Integer>
,Query
,QueryPart
,RowCountQuery
,Serializable
,Statement
public interface DropIndexOnStep extends DropIndexCascadeStep
A step in the construction of theDROP INDEX
statement.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
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method Description @NotNull DropIndexCascadeStep
on(String on)
Add theON
clause to theDROP INDEX
statement.@NotNull DropIndexCascadeStep
on(Name on)
Add theON
clause to theDROP INDEX
statement.@NotNull DropIndexCascadeStep
on(Table<?> on)
Add theON
clause to theDROP INDEX
statement.-
Methods inherited from interface org.jooq.Attachable
attach, configuration, detach
-
Methods inherited from interface org.jooq.AttachableQueryPart
getBindValues, getParam, getParams, getSQL, getSQL
-
Methods inherited from interface org.jooq.DropIndexCascadeStep
cascade, restrict
-
Methods inherited from interface org.jooq.Query
bind, bind, cancel, close, execute, executeAsync, executeAsync, isExecutable, keepStatement, poolable, queryTimeout
-
-
-
-
Method Detail
-
on
@Support({CUBRID,DERBY,FIREBIRD,H2,HSQLDB,MARIADB,MYSQL,POSTGRES,SQLITE,YUGABYTEDB}) @NotNull @CheckReturnValue @NotNull DropIndexCascadeStep on(@Name String on)
Add theON
clause to theDROP INDEX
statement.SQLDialect.MYSQL
,SQLDialect.MARIADB
, andSQLDialect#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.
-
on
@Support({CUBRID,DERBY,FIREBIRD,H2,HSQLDB,MARIADB,MYSQL,POSTGRES,SQLITE,YUGABYTEDB}) @NotNull @CheckReturnValue @NotNull DropIndexCascadeStep on(Name on)
Add theON
clause to theDROP INDEX
statement.SQLDialect.MYSQL
,SQLDialect.MARIADB
, andSQLDialect#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.
-
on
@Support({CUBRID,DERBY,FIREBIRD,H2,HSQLDB,MARIADB,MYSQL,POSTGRES,SQLITE,YUGABYTEDB}) @NotNull @CheckReturnValue @NotNull DropIndexCascadeStep on(Table<?> on)
Add theON
clause to theDROP INDEX
statement.SQLDialect.MYSQL
,SQLDialect.MARIADB
, andSQLDialect#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.
-
-