- All Superinterfaces:
Attachable
,AttachableQueryPart
,DDLQuery
,Flow.Publisher<Integer>
,Publisher<Integer>
,org.reactivestreams.Publisher<Integer>
,Query
,QueryPart
,RowCountQuery
,Serializable
,Statement
DROP 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 Summary
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.reactivestreams.Publisher
subscribe
Methods inherited from interface org.jooq.Query
bind, bind, cancel, execute, executeAsync, executeAsync, isExecutable, keepStatement, poolable, queryTimeout
-
Method Details
-
for_
@Support({DB2,DERBY,H2,HANA,HSQLDB,INFORMIX,ORACLE,SPANNER,SQLSERVER}) @NotNull @CheckReturnValue @NotNull DDLQuery for_(@Name String table) Add theFOR
clause to theDROP SYNONYM
statement.Specify the table for which to drop a synonym. In dialects where synonyms have a table namespace, this is mandatory. Otherwise, it will be ignored.
-
for_
@Support({DB2,DERBY,H2,HANA,HSQLDB,INFORMIX,ORACLE,SPANNER,SQLSERVER}) @NotNull @CheckReturnValue @NotNull DDLQuery for_(Name table) Add theFOR
clause to theDROP SYNONYM
statement.Specify the table for which to drop a synonym. In dialects where synonyms have a table namespace, this is mandatory. Otherwise, it will be ignored.
-
for_
@Support({DB2,DERBY,H2,HANA,HSQLDB,INFORMIX,ORACLE,SPANNER,SQLSERVER}) @NotNull @CheckReturnValue @NotNull DDLQuery for_(Table<?> table) Add theFOR
clause to theDROP SYNONYM
statement.Specify the table for which to drop a synonym. In dialects where synonyms have a table namespace, this is mandatory. Otherwise, it will be ignored.
-