Top Description Methods
org.jooq

public Interface DropIndexOnStep

extends DropIndexCascadeStep
Known Direct Implementers
org.jooq.impl.DropIndexImpl
Annotations
@SuppressWarnings:unused
Static Imports
org.jooq.SQLDialect.*, org.jooq.impl.DSL.*

Deprecated

as a consequence of DropIndexCascadeStep being deprecated. See corresponding docs for further information.

A step in the construction of the DROP INDEX statement.

Referencing XYZ*Step types directly from client code

It 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:

Method Summary

Modifier and TypeMethod and Description
public @NotNull DropIndexCascadeStep
on(String on)

Deprecated as a consequence of DropIndexCascadeStep being deprecated.
Add the ON clause to the DROP INDEX statement.
public @NotNull DropIndexCascadeStep
on(Name on)

Deprecated as a consequence of DropIndexCascadeStep being deprecated.
Add the ON clause to the DROP INDEX statement.
public @NotNull DropIndexCascadeStep
on(Table<?> on)

Deprecated as a consequence of DropIndexCascadeStep being deprecated.
Add the ON clause to the DROP INDEX statement.
Inherited from org.jooq.DropIndexCascadeStep:
cascaderestrict

Method Detail

onback to summary
public @NotNull DropIndexCascadeStep on(String on)

Deprecated

as a consequence of DropIndexCascadeStep being deprecated. See corresponding docs for further information.

Add the ON clause to the DROP INDEX statement.

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.

Annotations
@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
@NotNull
@CheckReturnValue
onback to summary
public @NotNull DropIndexCascadeStep on(Name on)

Deprecated

as a consequence of DropIndexCascadeStep being deprecated. See corresponding docs for further information.

Add the ON clause to the DROP INDEX statement.

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.

Annotations
@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
@NotNull
@CheckReturnValue
onback to summary
public @NotNull DropIndexCascadeStep on(Table<?> on)

Deprecated

as a consequence of DropIndexCascadeStep being deprecated. See corresponding docs for further information.

Add the ON clause to the DROP INDEX statement.

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.

Annotations
@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB
@NotNull
@CheckReturnValue