public interface AlterIndexOnStep extends AlterIndexStep
ALTER INDEX
where the table can be specified for
the index.
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:
Modifier and Type | Method and Description |
---|---|
@NotNull AlterIndexStep |
on(Name tableName)
Specify the table expression on which to alter an index.
|
@NotNull AlterIndexStep |
on(String tableName)
Specify the table expression on which to alter an index.
|
@NotNull AlterIndexStep |
on(Table<?> table)
Specify the table expression on which to alter an index.
|
renameTo, renameTo, renameTo
@NotNull @Support(value={DERBY,H2,HSQLDB,MARIADB,MYSQL,POSTGRES}) @NotNull AlterIndexStep 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.
@NotNull @Support(value={DERBY,H2,HSQLDB,MARIADB,MYSQL,POSTGRES}) @NotNull AlterIndexStep on(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.
@NotNull @Support(value={DERBY,H2,HSQLDB,MARIADB,MYSQL,POSTGRES}) @NotNull AlterIndexStep 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 © 2020. All rights reserved.