DROP TABLE

Drop the specified table.

Syntax

DROP [TEMPORARY] TABLE [IF EXISTS] <table_name> [FORCE];

Remarks

  • <table_name> is the name of a table in a SingleStore database.

  • This command can be run on the master aggregator node, or a child aggregator node (see Node Requirements for SingleStore Commands ).

  • This command causes implicit commits. Refer to COMMIT for more information.

  • If there is a view which depends on a table, the table cannot be dropped. See CREATE VIEW for more information.

  • By default, the DROP TABLE command waits for the running queries to finish before dropping the table. To override this behavior and kill any running queries, use the FORCE option.

  • Table memory can be freed when the DROP TABLE command is run.

    For information on when/how much table memory is freed when this command is run, see Managing Memory.

  • DROP TEMPORARY TABLE does not perform a COMMIT when run; issue a COMMIT prior to DROP TEMPORARY TABLE if there are uncommited statements.

  • Because temporary tables only exist for the duration of a client session, no access privileges are required to run DROP TEMPORARY TABLE.

  • Unlike when running the DROP TABLE command, running the DROP TEMPORARY TABLE command does not commit implicitly.

  • DROP TEMPORARY TABLE cannot drop global temporary tables.

  • A temporary or global temporary table can be dropped using DROP TABLE without specifying the TEMPORARY option.

  • Refer to the Permission Matrix for the required permission.

Example

DROP TABLE IF EXISTS mytbl;
DROP TABLE IF EXISTS tab1 FORCE;

Last modified: July 20, 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