Available in versions: Dev (3.21)
This documentation is for the unreleased development version of jOOQ. Click on the above version links to get this documentation for a supported version of jOOQ.
DROP PROCEDURE with signature
Applies to ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition
When working with a dialect that supports PROCEDURE overloading, the DROP PROCEDURE statement may need to be supplied with an explicit procedure signature, similar to the signature provided with the CREATE PROCEDURE statement. Some dialects may require only a list of parameter types without parameter names. jOOQ's API requires passing the complete parameter specification instead.
// Drop a procedure
create.dropProcedure("proc").parameters(in("p1", INTEGER), in("p2", INTEGER)).execute();
Dialect support
This example using jOOQ:
dropProcedure("p").parameters(in("p1", INTEGER), in("p2", INTEGER))
Translates to the following dialect specific expressions:
BigQuery, Firebird, HSQLDB, Hana, MariaDB, MySQL, Oracle, SQLDataWarehouse, SQLServer
DROP PROCEDURE p
DB2
DROP PROCEDURE p( integer, integer )
Informix
DROP PROCEDURE p( p1 integer, p2 integer )
Postgres, YugabyteDB
DROP PROCEDURE p( p1 int, p2 int )
Snowflake
DROP PROCEDURE p( number, number )
ASE, Access, Aurora MySQL, Aurora Postgres, ClickHouse, CockroachDB, Databricks, Derby, DuckDB, Exasol, H2, MemSQL, Redshift, SQLite, Sybase, Teradata, Trino, Vertica
/* UNSUPPORTED */
Generated with jOOQ 3.21. Support in older jOOQ versions may differ. Translate your own SQL on our website
Feedback
Do you have any feedback about this page? We'd love to hear it!