- All Superinterfaces:
CreateTriggerActionStep
,CreateTriggerWhenStep
- All Known Subinterfaces:
CreateTriggerReferencingStep
A step in the construction of the Referencing
CREATE 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 TypeMethodDescription@NotNull CreateTriggerWhenStep
Add theFOR EACH ROW
clause to theCREATE TRIGGER
statement.@NotNull CreateTriggerWhenStep
Add theFOR EACH STATEMENT
clause to theCREATE TRIGGER
statement.Methods inherited from interface org.jooq.CreateTriggerActionStep
as, as, as
-
Method Details
-
forEachRow
@Support({AURORA_POSTGRES,DB2,DERBY,FIREBIRD_3_0,HSQLDB,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,YUGABYTEDB}) @NotNull @CheckReturnValue @NotNull CreateTriggerWhenStep forEachRow()Add theFOR EACH ROW
clause to theCREATE TRIGGER
statement. -
forEachStatement
@Support({AURORA_POSTGRES,DB2,DERBY,HSQLDB,ORACLE,POSTGRES,SQLSERVER}) @NotNull @CheckReturnValue @NotNull CreateTriggerWhenStep forEachStatement()Add theFOR EACH STATEMENT
clause to theCREATE TRIGGER
statement.
-