Sign inTry Free

Important

New database features are no longer connected to engine versions; features are now enabled independently during scheduled update windows, and “major” and “minor” releases no longer exist in Helios. Please visit the release notes to view the latest features available in your database clusters.

PARAMETERS

This view contains information about parameters.

Column Name

Description

SPECIFIC_CATALOG

The name of the catalog that a given parameter belongs to.

SPECIFIC_SCHEMA

The name of the related schema (database) for a given parameter.

SPECIFIC_NAME

The name of the routine which contains a given parameter.

ORDINAL_POSITION

The position of a given parameter among others in a given stored procedure or other object containing a parameter.

PARAMETER_MODE

The mode of a given parameter.

PARAMETER_NAME

The name of a given parameter.

DATA_TYPE

The data type of a given parameter.

CHARACTER_MAXIMUM_LENGTH

The maximum length, in characters, for a given string parameter.

CHARACTER_OCTET_LENGTH

The maximum length, in bytes, for a given string parameter.

NUMERIC_PRECISION

The numeric precision (maximum number of digits present in a number) for a given parameter.

NUMERIC_SCALE

The numeric scale (maximum number of digits to the right the decimal point in a number) for a given parameter.

CHARACTER_SET_NAME

The name of the related character set for a given parameter.

COLLATION_NAME

The name of the related collation for a given parameter.

DTD_IDENTIFIER

This field contains the data type of a given parameter, as well as other low level information.

ROUTINE_TYPE

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

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