Sign inTry Free

Important

Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.

DROP PROJECTION

On this page

Note

This is a Preview feature.

The DROP PROJECTION command drops an existing projection.

Syntax

DROP PROJECTION [IF EXISTS] <projection_name> ON [database_name.]<table_name>

Arguments

  • projection_name: The name of the projection that was created using the CREATE PROJECTION command.

  • database_name: The database where the projection's base table is located. This argument is optional.

  • table_name: The name of the table the projection is created on.

  • IF EXISTS: Use the IF EXISTS clause to delete a projection only if it exists on the specified table. When IF EXISTS is specified:

    • If the projection exists on the table in the ON clause, it is deleted.

    • If the projection does not exist on the specified table, the command makes no changes and completes successfully.

    • If the table in the ON clause does not exist, DROP PROJECTION returns an error.

Example

  • Delete a projection.

    DROP PROJECTION lineitem_sort_shipdate ON lineitem;

  • Database names can be referenced in the DROP PROJECTION command.

    DROP PROJECTION lineitem_sort_shipdate ON testdb1.lineitem;

  • Attempt the delete operation only if a projection exists on the specified table:

    DROP PROJECTION IF EXISTS lineitem_sort_shipdate ON lineitem;

Last modified:

Was this article helpful?

On this page

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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In