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.

BSON Data Type Mapping

On this page

SingleStore Kai natively supports the BSON data type for storage.

Note

The BSON type and BSON-specific functions must only be used for directly querying tables created by SingleStore Kai using SQL.

BSON Type Conversion

  • For all BLOB/string to BSON casting, SingleStore interprets the source as raw BSON bytes.

  • For JSON to BSON casting, SingleStore converts the JSON data according to the MongoDB® Extended JSON V2 format (Relaxed or Canonical).

  • BSON can be casted to JSON using the :>JSON notation. This conversion is performed in the MongoDB® Extended JSON V2 Relaxed format.

The following table maps SingleStore data types to the corresponding BSON data types :

SingleStore Data Type

BSON Data Type

BIGINT

INT64

BINARY

BINARY (subtype 0)

BIT

INT32 or INT64

BLOB

BINARY

CHAR

STRING

DATE

DATETIME

DATETIME

DATETIME

DATETIME(6)

DATETIME

DECIMAL

INT32, INT64, DOUBLE, or DECIMAL (based on size)

DOUBLE

DOUBLE

ENUM

STRING

FLOAT

DOUBLE

GEOGRAPHY

STRING

GEOGRAPHYPOINT

STRING

INT

INT32

JSON

BSON

LONGBLOB

BINARY

LONGTEXT

STRING

MEDIUMBLOB

BINARY

MEDIUMINT

INT32

MEDIUMTEXT

STRING

SMALLINT

INT32

TEXT

STRING

TIME

STRING

TIMESTAMP

DATETIME

TIMESTAMP6

DATETIME

TINYBLOB

BINARY

TINYINT

BOOLEAN

TINYTEXT

STRING

VARBINARY

BINARY

VARCHAR

STRING

VECTOR(F32)

BSON Array of DOUBLE type elements

VECTOR(F64)

BSON Array of DOUBLE type elements

VECTOR(I8)

BSON Array of INT32 type elements

VECTOR(I16)

BSON Array of INT32 type elements

VECTOR(I32)

BSON Array of INT32 type elements

VECTOR(I64)

BSON Array of INT64 type elements

YEAR

INT32

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