DROP PROCEDURE

Removes a single stored procedure from the specified database.

Syntax

DROP PROCEDURE [IF EXISTS] { procedure_name | database_name.procedure_name }

Remarks

  • Only one stored procedure can be removed using the DROP PROCEDURE command.

  • If DROP PROCEDURE is executed for a procedure that does not exist, the following error will occur:

    DROP PROCEDURE myprocedure;
    ERROR 1998 (HY000): Function 'db1.myprocedure' doesn't exist
  • However, if the IF EXISTS condition is used and the procedure does not exist, no error will occur:

    DROP PROCEDURE IF EXISTS myprocedure;
    Query OK, 0 rows affected (0.00 sec)
  • This command causes implicit commits. Refer to COMMIT for more information.

  • Refer to the Permission Matrix for the required permission.

Examples

Dropping a Procedure in the Current Database

The following example removes an existing function from the current database.

SHOW FUNCTIONS;
+------------------+------------------+
| Functions_in_db1 | Function Type    |
+------------------+------------------+
| myprocedure      | Stored Procedure |
+------------------+------------------+
1 row in set (0.00 sec)
DROP PROCEDURE myprocedure;
SHOW FUNCTIONS;
Query OK, 0 rows affected (0.07 sec)

Dropping a Procedure in Another Database

The following example removes an existing stored procedure while connected to another database in your SingleStore cluster.

USE db1;
SHOW FUNCTIONS;
+------------------+------------------+
| Functions_in_db1 | Function Type    |
+------------------+------------------+
| myprocedure      | Stored Procedure |
+------------------+------------------+
1 row in set (0.00 sec)
USE db2;
DROP PROCEDURE db1.myprocedure;
USE db1;
SHOW FUNCTIONS;
Query OK, 0 rows affected (0.07 sec)

Related Topics

Last modified: May 22, 2023

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK