A step in the construction of the Referencing
CREATE SYNONYM
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
-
for_
@Support({DB2,DERBY,H2,HANA,HSQLDB,INFORMIX,ORACLE,SQLSERVER}) @NotNull @CheckReturnValue @NotNull DDLQuery for_(@Name String table) Add theFOR
clause to theCREATE SYNONYM
statement. -
for_
@Support({DB2,DERBY,H2,HANA,HSQLDB,INFORMIX,ORACLE,SQLSERVER}) @NotNull @CheckReturnValue @NotNull DDLQuery for_(Name table) Add theFOR
clause to theCREATE SYNONYM
statement. -
for_
@Support({DB2,DERBY,H2,HANA,HSQLDB,INFORMIX,ORACLE,SQLSERVER}) @NotNull @CheckReturnValue @NotNull DDLQuery for_(Table<?> table) Add theFOR
clause to theCREATE SYNONYM
statement.
-