- All Known Subinterfaces:
- CreateTriggerForStep,- CreateTriggerReferencingStep,- CreateTriggerWhenStep
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 Details- 
as@Support({AURORA_POSTGRES,DB2,DERBY,FIREBIRD_3_0,HSQLDB,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,YUGABYTEDB}) @NotNull @CheckReturnValue @NotNull DDLQuery as(Statement... body) Add theASclause to theCREATE TRIGGERstatement.
- 
as@Support({AURORA_POSTGRES,DB2,DERBY,FIREBIRD_3_0,HSQLDB,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,YUGABYTEDB}) @NotNull @CheckReturnValue @NotNull DDLQuery as(Collection<? extends Statement> body) Add theASclause to theCREATE TRIGGERstatement.
- 
as@Support({AURORA_POSTGRES,DB2,DERBY,FIREBIRD_3_0,HSQLDB,MARIADB,MYSQL,ORACLE,POSTGRES,SQLITE,SQLSERVER,YUGABYTEDB}) @NotNull @CheckReturnValue @NotNull DDLQuery as(Statement body) Add theASclause to theCREATE TRIGGERstatement.
 
-