Sign inTry Free

SingleStore Client

On this page

Overview

The singlestore-client package contains is a lightweight client application that allows you to run SQL queries against your database from a terminal window.

Refer to SingleStore Client Installation for information on installing, upgrading, or uninstalling the client. After installing the singlestore-client, use the singlestore command to connect to your SingleStore database.

The singlestore command is a wrapper script that starts the singlestore-client binary with predefined connection options, including --no-defaults. Use singlestore --help to view additional supported connection options.

While the following options may appear in the output of singlestore --help, these are not supported by the singlestore command (wrapper):

  • --defaults-file

  • --defaults-extra-file

  • --defaults-group-suffix

  • --no-defaults (implicitly applied)

  • --login-path

These options are only supported as leading arguments in the command line. Because the singlestore wrapper inserts its own options before the user-specified arguments, these options are not treated as leading arguments and are rejected by the option parser. Consequently, the singlestore command does not read MySQL option files, such as my.cnf.

To use an option file for connection configuration or credentials, run the singlestore-client binary directly and specify --defaults-file as the first option. For example:

/usr/lib/singlestore-client/singlestore-client \
  --defaults-file=/path/to/file.cnf

If the client was installed from a tarball, the singlestore-client binary is located in the lib directory within the extracted directory.

For more connection options, help is available through singlestore --help.

singlestore -h <Master-or-Child-Aggregator-host-IP-address> -P <port> -u <user> -p<secure-password>
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 12
Server version: 5.7.32 SingleStoreDB source distribution (compatible; MySQL Enterprise & MySQL Commercial)

Copyright (c) 2000, 2022, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

singlestore>

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