Sign inTry Free

Warning

SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

TABLES

This view contains information about the tables visible to the current node.

Column Name

Description

TABLE_CATALOG

Always = def.

TABLE_SCHEMA

The database the table belongs to (could be partitioned database, i.e., db_0).

TABLE_NAME

Name of the table.

TABLE_TYPE

The type of the table (i.e., SYSTEM VIEW, VIEW, TEMPORARY TABLE, GLOBAL TEMPORARY TABLE, or BASE TABLE).

ENGINE

Always = MemSQL.

VERSION

NULL (currently unsupported).

ROW_FORMAT

COMPRESSION = SPARSE if sparse compression is used.

TABLE_ROWS

Row count for the table.

AVG_ROW_LENGTH

NULL (currently unsupported).

DATE_LENGTH

NULL (currently unsupported).

MAX_DATA_LENGTH

NULL (currently unsupported).

INDEX_LENGTH

NULL (currently unsupported).

DATA_FREE

NULL (currently unsupported).

AUTO_INCREMENT

The auto increment counter of the auto increment column (or NULL if not in use).

CREATE_TIME

Time the table was created (SQL timestamp).

UPDATE_TIME

NULL (currently unsupported).

CHECK_TIME

NULL (currently unsupported).

TABLE_COLLATION

NULL (currently unsupported).

CHECKSUM

NULL (currently unsupported).

CREATE_OPTIONS

NULL (currently unsupported).

TABLE_COMMENT

Comment from the CREATE TABLE statement, if specified.

DISTRIBUTED

1 if table is sharded, 0 otherwise.

STORAGE_TYPE

COLUMNSTORE for columnstore databases. INMEMORY_ROWSTORE for rowstore.

ALTER_TIME

Time of the most recent change to the table (SQL timestamp) or the CREATE_TIME if the table has not been altered.

ALTER_USER

Name of the user that made the most recent change to the table.

CREATE_USER

Name of the user that created the table.

Last modified: October 5, 2022

Was this article helpful?

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