Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

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, while SingleStore 9.0 is recommended for production workloads.

LIKE, NOT LIKE

On this page

The LIKE and NOT LIKE operators are useful for matching patterns containing simple wildcards.

The % character appearing in a pattern matches any string and the _ character matches a single character. For example:

CREATE TABLE like_s (b int, t varchar(20));
INSERT INTO like_s VALUES(0, 'red'), (1, 'blue');
SELECT * FROM like_s WHERE t LIKE 'r_d';
+------+------+
| b    | t    |
+------+------+
|    0 | red  |
+------+------+
SELECT * FROM like_s WHERE t NOT LIKE 'r%';
+------+------+
| b    | t    |
+------+------+
|    1 | blue |
+------+------+

You can use the backslash character \ as an escape character with a LIKE operator so that SingleStore interprets the wildcard character as a literal character. For example:

SELECT "foo_" LIKE "foo\_";
+---------------------+
| "foo_" LIKE "foo\_" |
+---------------------+
|                   1 |
+---------------------+

Warning

Implicit Collation

When character_set_server is set to utf8, string literals with characters using 4-byte encoding are implicitly assigned binary collation and processed as a sequence of bytes rather than characters. This implicit conversion to binary collation causes string functions to return unexpected results. To avoid using implicit binary collation, either use explicit type casting or use database columns defined with the utf8mb4 character set.

For more information, refer to Implicit Collation in Special Cases.

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