Module org.jooq

Package org.jooq

Interface DropTriggerOnStep

All Superinterfaces:

Attachable, AttachableQueryPart, DDLQuery, Flow.Publisher<Integer>, Publisher<Integer>, org.reactivestreams.Publisher<Integer>, Query, QueryPart, RowCountQuery, Serializable, Statement

@Pro
public interface DropTriggerOnStep
extends DDLQuery

A step in the construction of the DROP TRIGGER 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:

• 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

Modifier and Type	Method	Description
@NotNull DDLQuery	on(String on)	Add the ON clause to the DROP TRIGGER statement.
@NotNull DDLQuery	on(Name on)	Add the ON clause to the DROP TRIGGER statement.
@NotNull DDLQuery	on(Table<?> on)	Add the ON clause to the DROP TRIGGER 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.Publisher

subscribe

Methods inherited from interface org.reactivestreams.Publisher

subscribe

Methods inherited from interface org.jooq.Query

bind, bind, cancel, execute, executeAsync, executeAsync, isExecutable, keepStatement, poolable, queryTimeout

Methods inherited from interface org.jooq.QueryPart

$replace, $replace, $traverse, $traverse, equals, hashCode, toString

Method Details

on

@Support({AURORA_POSTGRES,DB2,DERBY,FIREBIRD_3_0,HSQLDB,INFORMIX,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,YUGABYTEDB})
@NotNull
@CheckReturnValue
@NotNull DDLQuery on(@Name
 String on)

Add the ON clause to the DROP TRIGGER statement.

SQLDialect.POSTGRES uses table-scoped trigger names, not schema-scoped names. This means that in these databases, the ON clause is mandatory in order to unambiguously identify a trigger. In all other databases, the ON clause will simply be ignored for compatibility reasons.

on

@Support({AURORA_POSTGRES,DB2,DERBY,FIREBIRD_3_0,HSQLDB,INFORMIX,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,YUGABYTEDB})
@NotNull
@CheckReturnValue
@NotNull DDLQuery on(Name on)

Add the ON clause to the DROP TRIGGER statement.

SQLDialect.POSTGRES uses table-scoped trigger names, not schema-scoped names. This means that in these databases, the ON clause is mandatory in order to unambiguously identify a trigger. In all other databases, the ON clause will simply be ignored for compatibility reasons.

on

@Support({AURORA_POSTGRES,DB2,DERBY,FIREBIRD_3_0,HSQLDB,INFORMIX,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,YUGABYTEDB})
@NotNull
@CheckReturnValue
@NotNull DDLQuery on(Table<?> on)

Add the ON clause to the DROP TRIGGER statement.

SQLDialect.POSTGRES uses table-scoped trigger names, not schema-scoped names. This means that in these databases, the ON clause is mandatory in order to unambiguously identify a trigger. In all other databases, the ON clause will simply be ignored for compatibility reasons.