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.

ROUTINES

This view contains information about routines in a cluster.

Column Name

Description

SPECIFIC_NAME

The name of a given routine.

ROUTINE_CATALOG

The related catalog for a given routine.

ROUTINE_SCHEMA

The related schema (database) for a given routine.

ROUTINE_NAME

The name of a given routine.

ROUTINE_TYPE

The type of routine a given parameter is associated with: PROCEDURE or FUNCTION.

DATA_TYPE

The data type of a given routine. If a routine is the PROCEDURE type, this column is NULL.

CHARACTER_MAXIMUM_LENGTH

The maximum length, in number of characters, returned by a given routine. If a routine is the PROCEDURE type, this column is NULL.

CHARACTER_OCTET_LENGTH

The maximum length, in bytes, returned by a given routine. If a routine is the PROCEDURE type, this column is NULL.

NUMERIC_PRECISION

The numeric precision (maximum number of digits present in a number) for the return of a given routine. If a routine is the PROCEDURE type, this column is NULL.

NUMERIC_SCALE

The numeric scale (maximum number of digits to the right the decimal point in a number) for the return to a given routine. If a routine is the PROCEDURE type, this column is NULL.

CHARACTER_SET_NAME

The related character set name returned by a given routine. If a routine is the PROCEDURE type, this column is NULL.

COLLATION_NAME

The related collation name returned by a given routine. If a routine is the PROCEDURE type, this column is NULL.

DTD_IDENTIFIER

The data type returned by a given routine. If a routine is the PROCEDURE type, this column is NULL.

ROUTINE_BODY

The language used to define a given routine. This value is always SQL.

ROUTINE_DEFINITION

The SQL statement executed by a given routine.

EXTERNAL_NAME

This value is always NULL.

EXTERNAL_LANGUAGE

The language of the routine. This value is always SQL.

PARAMETER_STYLE

This value is always SQL.

SQL_PATH

This value is always NULL.

SECURITY_TYPE

This value is always DEFINER.

CREATED

The timestamp at which a given routine was created.

LAST_ALTERED

The timestamp at which a given routine was last updated.

SQL_MODE

The setting of the SQL_mode engine variable at the creation of a given routine.

ROUTINE_COMMENT

Comments (if any) left during the creation of a given routine.

DEFINER

The user who created a given routine.

CHARACTER_SET_CLIENT

This column is only included for command compatibility with MySQL. The value of this variable cannot be guaranteed.

COLLATION_CONNECTION

The setting of the collation_connection engine variable at the creation of a given routine.

DATABASE_COLLATION

The related collation for a given routine.

DATETIME_PRECISION

The fractional-seconds precision of the column: 0 for TIME, TIMESTAMP, DATETIME and 6 for DATETIME(6) columns, or NULL if the column not a time data type.

Last modified:

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

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