1. dialects
prorm
  • prorm documentation
  • Known test gaps
  • Architecture
  • Core concepts
  • Database types & coverage
  • Getting started
  • Going further
  • compliance
    • Compliance
    • The security toolkit: `prorm audit`
    • Checklists by regulation
    • Declaring personal data
    • Evidence bundles
    • Evidence
    • Frameworks: `@Security`
    • Jurisdictions
    • Platform policies
    • Protecting data
    • The regulation dataset
    • Residency and cross-border transfers
    • Retention & integrity
    • Status
    • Subject rights
  • decorators
    • prorm with decorators
    • Models with decorators
    • Querying a decorated model
    • Relations with decorators
  • diagrams
    • Diagram generators
    • Chen diagram
    • Class diagram
    • Dependency diagram
    • ER diagram
    • Flow diagram
    • From your models to a diagram
    • Gantt diagram
    • Index diagram
    • Migration diagram
    • Model diagram
    • Package diagram
    • Crow’s-foot diagram
    • Schema documentation
    • Sequence diagram
    • State diagram
    • Tree diagram
  • dialects
    • SQL dialects
    • AlloyDB Dialect
    • AlloyDB Omni Dialect
    • Amazon Athena Dialect
    • Aurora DSQL Dialect
    • Amazon Aurora MySQL Dialect
    • Amazon Aurora PostgreSQL Dialect
    • Azure Database for MySQL Dialect
    • Azure Database for PostgreSQL Dialect
    • Azure SQL Database Dialect
    • Azure SQL Managed Instance Dialect
    • Google BigQuery Dialect
    • Citus Dialect
    • ClickHouse dialect
    • Cloud Authentication (`cloud-auth`)
    • Cloud SQL for SQL Server Dialect
    • Cloud SQL for MySQL Dialect
    • Cloud SQL for PostgreSQL Dialect
    • CockroachDB Dialect
    • Azure Cosmos DB for PostgreSQL Dialect
    • CrateDB Dialect
    • Cloudflare D1 Dialect
    • Databricks dialect
    • IBM Db2 Dialect
    • Dolt Dialect
    • Apache Doris Dialect
    • Druid Dialect
    • DuckDB Dialect
    • Exasol dialect
    • Microsoft Fabric Data Warehouse Dialect
    • Firebird Dialect
    • Greenplum Dialect
    • SAP HANA Dialect
    • MySQL HeatWave Dialect
    • Azure Data Explorer (Kusto) Dialect — T-SQL
    • MariaDB Dialect
    • Materialize Dialect
    • MonetDB Dialect
    • MotherDuck Dialect
    • Microsoft SQL Server Dialect
    • MySQL Dialect
    • Neon Dialect
    • OceanBase Dialect
    • openGauss Dialect
    • Oracle Dialect
    • Oracle Autonomous Database Dialect
    • ParadeDB Dialect
    • PolarDB Dialect
    • PostgreSQL Dialect
    • Presto Dialect
    • QuestDB Dialect
    • Aurora RDS Data API Dialect (`rdsdata`)
    • Amazon RDS for Db2 Dialect
    • Amazon RDS for MariaDB Dialect
    • Amazon RDS for SQL Server Dialect
    • Amazon RDS for MySQL Dialect
    • Amazon RDS for Oracle Dialect
    • Amazon RDS for PostgreSQL Dialect
    • Amazon Redshift
    • Amazon Redshift Data API Dialect
    • RisingWave Dialect
    • rqlite Dialect
    • SingleStore Dialect
    • Snowflake Dialect
    • Google Cloud Spanner Dialect
    • Spanner (PostgreSQL interface) Dialect
    • SQLite Dialect
    • StarRocks Dialect
    • Supabase Dialect
    • Azure Synapse Analytics (dedicated SQL pool)
    • Teradata Dialect
    • TiDB Dialect
    • TimescaleDB Dialect
    • Trino Dialect
    • Turso / libSQL Dialect
    • Vertica dialect
    • Vitess Dialect
    • Yellowbrick Dialect
    • YugabyteDB Dialect
  • guides
    • Access rules and behaviour profiles
    • ArangoDB (AQL)
    • Associations
    • Audit levels and escalation
    • Audit logging
    • In the browser
    • Bulk operations
    • Caching
    • Capabilities, tiers and team roles
    • CLI
    • Cloudflare
    • Compliance & data protection
    • Connection Pooling & Performance
    • Security in the console
    • Couchbase: structured N1QL queries
    • Data types
    • Decorators
    • Eager loading
    • Enums and constants
    • Error handling & error types
    • Extensions
    • External fields
    • Foreign data wrappers
    • Graph databases
    • Hooks & lifecycle events
    • Indexes & constraints
    • InfluxDB: structured Flux pipelines
    • klock-errors
    • klock — the `.klock` file
    • Local databases (`prorm db up`)
    • Structured log search — Splunk, Graylog, Papertrail, Sumo Logic
    • Logging
    • Grafana Loki: structured LogQL queries
    • MCP server
    • Migrate — the data transfer subsystem
    • Migrations & Schema Sync
    • Models from an existing database
    • Defining models
    • Multiple databases
    • OrientDB, Neptune and TigerGraph
    • Passwords
    • Importing a Prisma schema
    • Structured PromQL and MetricsQL
    • Query firewall
    • QueryInterface
    • Query operators reference
    • Query optimization
    • Composing find options with `pipe()` and `Q`
    • Query safety: the fail-closed WHERE guard
    • Querying
    • Raw Queries & Query Building
    • Read replicas
    • Schema diffing & migration generation
    • Views, triggers & other schema objects
    • Scopes & default scopes
    • Seeders
    • SPARQL / RDF triplestores
    • SQL constants
    • SQL features
    • SQL function builders
    • SQLite advanced features
    • StoreKey — a prod-orm database as the storage
    • Streaming results
    • Terraform
    • Transactions & Isolation Levels
    • Type mapping: legacy and modern
    • TypeScript types
    • Database users, roles & privileges
    • Validation & constraints
    • Virtual & Computed Fields
    • Writing docs
  • javascript
    • prorm in JavaScript
    • Models in JavaScript
    • Querying in JavaScript
    • Relations in JavaScript
  • runbooks
    • Operational runbooks
    • Connection failures
    • Credential rotation
    • Failover
    • Incident checklist
    • Deploying klock v2
    • Migration rollback
  • running-databases
    • Running databases in Docker
    • Running prorm under Bun in Docker
    • Running Cassandra in Docker with prorm
    • Running ClickHouse in Docker with prorm
    • Running CockroachDB in Docker with prorm
    • Running prorm under Deno in Docker
    • Running Elasticsearch in Docker with prorm
    • Running MariaDB in Docker with prorm
    • Running MongoDB in Docker with prorm
  • prorm control plane
    • Introduction
    • Authentication
    • Errors
    • Getting started
      • Service
        • Is it up
        • This description
    • Account
      • Sign-up and verification
        • Create an account
        • Exchange credentials for a token
        • Verify with the emailed code
        • Verify by clicking the emailed link
        • Name the parent or guardian
        • What a consent link is about
        • Give consent for a child's account
        • Ask the parent or guardian again
        • Send a new code and link
      • Family
        • Everyone this account is responsible for
        • One child, in detail
        • Turn a limit on or off
      • Profile
        • Who am I
        • Change the account
        • Every address on the account
        • Add an address
        • Confirm an address with the code mailed to it
        • Mail a fresh code to an unconfirmed address
        • Make an address primary
        • Remove an address
        • What this caller may do
    • Security
      • Sessions
        • Everywhere this account is signed in
        • Sign out everywhere else
        • Sign one out
        • A token for the CLI on a named machine
        • A token for the customer console, from the staff one
        • Park a sign-in for the CLI to collect
        • The CLI collecting its sign-in
        • The team's members' live sessions
        • Sign a member's session out
        • Sign an account out everywhere
        • Everywhere the account is signed in
        • Sign an account's session out
      • Single sign-on
        • Begin a single sign-on
        • The provider's return
        • Link the signed-in account to a team's provider
        • Which team an address signs in to
        • The team's single sign-on, as a member sees it
        • Set the team's OpenID Connect provider up, or change it
        • Remove the provider
        • The team's domain claims and the DNS record each needs
        • Prove a claimed domain
      • MFA and passwords
        • Start enrolling a second factor
        • Prove the app has it
        • Remove the second factor
        • Ask for a reset link
        • Set a new password with the emailed token
      • Klock
        • Open a device-bound klock session
        • Check in, for the next grant
        • Step up the session asking
        • Rotate the device key
        • Freeze a session
        • Unfreeze a session
        • A guest grant
        • The revocation feed
        • The published keyset
        • What this control plane supports
      • Devices
        • Your devices, or a team's
        • Approve a new device's pairing code
        • One device
        • Rename a device
        • Revoke a device
        • Suspend a device
        • Reinstate a suspended device
        • Wipe a device
        • Ask a device to rotate its key
        • The team's members' devices
        • Revoke a member's device
        • An account's devices
        • Revoke an account's device
        • Wipe an account's device
        • The device fleet
      • Access rules and behaviour
        • The access rules that bear on you
        • Add an access rule
        • This request, as the rules see it
        • One access rule
        • Remove an access rule
        • The behaviour profiles that bear on you
        • Add or change a behaviour profile
        • The profile presets
        • Your behaviour findings
        • Acknowledge a finding
        • One behaviour profile
        • Remove a behaviour profile
        • The team's access rules
        • Add a team access rule
        • Remove a team access rule
        • The team's behaviour profiles
        • Add or change a team behaviour profile
        • Remove a team behaviour profile
        • What the team's profiles caught
        • Acknowledge a team finding
      • Recovery and lockdown
        • Ask for a recovery link
        • Recover access with the emailed code
        • Is the account locked down
        • Lock the account down
        • Release a lockdown
        • Lock a member down
        • Release a member's lockdown
      • MCP tokens
        • Make a delegated token for one MCP client
        • The account's delegated tokens
        • Revoke a delegated token
        • What a delegated token may do now
        • Run one MCP tool with a delegated token
        • Run a device-signed MCP tool call relayed by the MCP Worker
      • Kerberos
        • Give the team its own Kerberos realm
        • The team's realm
        • Remove the team's realm
    • Logging and monitoring
      • Audit log
        • What has been done to the account
        • What has happened to this account
        • The account's audit trail
      • Operations
        • Everything that has been asked of this database
        • One, with its steps
        • Stop it
        • Put a failed one back in the queue
        • Every operation, across all accounts
      • Metrics and events
        • Every measurement, for a graph
        • Who did what to it
    • Billing
      • Plans and pricing
        • What the plans allow
        • The rate card
        • What one database would cost
        • What this account is paying for, itemised
      • Subscriptions and invoices
        • What this month's invoice will say
        • What this account is on
        • What it has been charged
        • Start a Stripe Checkout session
        • Open the customer portal
        • Stripe's events
        • Buy more connection pools
      • Team billing
        • The team's billing account
        • What the team has been charged
        • What this month's invoice will say
        • The team's cards
        • Add a card, through a Stripe-hosted setup session
        • Make a card the team's default
        • Remove a card
        • Start the team paying
        • Open the Stripe portal on the team's customer
        • Change the team's plan
        • Who receives the team's bills
        • How the team pays for transfers
    • Support
      • Support chat
        • My conversations
        • Start a conversation
        • Every support conversation, open first
        • A ticket for the socket
        • One conversation, with who is in it and who is connected
        • Rename a group; open or close a support conversation
        • The lines, oldest first
        • Say something
        • Add somebody
        • Mark read
    • Administration
      • Users
        • Every account
        • One account, with everything hanging off it
        • Grant or revoke admin
        • Verify an account by hand
        • Lock or unlock sign-in
        • Allow or hold provisioning
        • Send the verification mail again
        • Set the plan by hand
      • Platform
        • Every database and store, across all accounts
        • The counts worth putting on a dashboard
      • Staff and permissions
        • What kind of admin the caller is, and which scopes they hold
        • The admin presets
        • Every admin, and the scopes each resolves to
        • Make an account an admin of a kind
        • Change an admin's kind, or a custom admin's scopes
        • Revoke admin
      • Team administration
        • Every team, with its owner and size
        • One team in full — members with their accounts, and projects
        • Hand the team to another member
        • Put an account in the team, active at once
        • Change a member's role
        • Remove a member
      • Assumed identities
        • Assume an identity — act as a customer account
        • The identities the caller holds open
        • End an assumed identity
      • Support inbox
        • The platform's addresses
        • Add a platform address
        • One address, with its counts
        • Change an address's label, routing, or whether it accepts mail
        • Remove an address that holds no mail
        • Make, adopt or repair the address's routing rule
        • Every admin's personal address, made where missing
        • File a raw message, as if it had arrived
        • The inbox
        • One message, whole
        • Mark a message
        • Hand a message to an admin, or take it back
        • Leave an internal note
        • Reply, from the address the message came to
        • What is waiting
    • Databases
      • Databases
        • Data stores
          • Every data store on the account
          • Provision a data store
          • Change a data store that is already running
          • One data store
          • Deprovision it
          • Report what it is using
          • How to reach a data store
        • Connections and credentials
          • The api keys on a database
          • Issue a key
          • Revoke a key
          • The engine users we created
          • Create a user inside the database
          • Give a user a new password
          • Drop a user
          • How the database is reached
          • Set how it is reached
          • Revoke every api key on it
          • How to connect to it
          • The ssh keys that open its bastion
          • Add a key, or have one made
          • The private half of a generated key, once
          • Revoke an ssh key
        • Schema and objects
          • The SQL objects we put in it
          • Create one, and apply it
          • What is in the database, as the engine reports it
          • One table
          • What it would run, without running it
          • Redefine an object in place
          • Drop it
          • The extensions installed in it
        • Migrations
          • A plan compiled to statements, recording nothing
          • The migrations recorded for it
          • Record one
          • Apply everything recorded and not yet run
          • Apply everything pending, oldest version first
        • Lifecycle
          • Grow or shrink it
          • Stop it accepting connections
          • Start it again
          • Move it to another region
        • Backups and replicas
          • Take a backup
          • The backups it has
          • Restore one into it
          • What has been restored into it, and from where
          • Its read copies
          • Add one
        • Policies
          • The catalog
          • One policy
          • What this database is held to
          • Switch a policy on, or change its knobs
          • Switch it off
          • Mark the policies reviewed
          • Evaluate the periodic policies now
          • Who is behind a credential
        • Passwordless
          • The database's passwordless sessions
          • Issue a passwordless session (v1)
          • Revoke a passwordless session
          • Bind a session to a device key
          • Issue a v2 session for a host to bind
          • Redeem an enrolment ticket on the host
          • Check a passwordless credential
          • Run one described query under a passwordless credential
        • Database roles
          • The database's roles
          • Define a role
          • One role
          • Change what a role permits
          • Delete a role, and revoke every key granted it
          • Grant a role, which mints a key
          • Who holds a role
          • The api keys bound to a role
        • Pools
          • A database's connection pools, and how busy each is
          • Open another pool
          • Rename a pool or change its size
          • Close a pool
        • Data plane
          • Run a query against a database
          • Several statements, in order, over one connection
          • Is this database answering
          • What the proxy itself is holding
        • Transfers
          • The strategies this account's tier may use
          • Price a transfer without creating it
          • The account's transfer jobs, newest first
          • Create a transfer job
          • One job, and whether its certificate holds
          • Cancel an unfinished job
          • Start a created job, confirming its price
          • Report a job's status (the runner, or the owner's side of a local run)
        • Every database on the account
        • Provision a database
        • Change a database that is already running
        • One database
        • Deprovision it
        • Read or write it
        • Report what it is using
        • The engines this API will provision
        • Where a managed database can be put
    • Teams
      • Teams
        • Members
          • Who is on it
          • Invite somebody
          • Accept an invitation
          • Change somebody's role
          • Remove somebody
        • Projects
          • The projects a team runs
          • Start one
          • Rename a project, or move its environment
          • Delete a project
          • One project, and what is in it
          • Put a database or store in it
          • What is in a project
          • Take one out
        • The teams this account is on
        • Start one
        • The twelve roles, and what each may do
        • Rename a team
        • Close a team
        • One team
        • Hand the team to somebody else
        • Leave a team
    • Schemas
      • Error
      • ValidationErrors
      • Token
      • PolicyCategory
      • PolicySeverity
      • PolicyAction
      • PolicyTrigger
      • PolicyParam
      • Policy
      • PolicyCatalog
      • PolicyAssignment
      • PolicyOutcome
      • PolicyFiring
      • CredentialTrace
      • Relation
      • Restrictions
      • ChildSummary
      • SignupRequest
      • SigninRequest
      • UpdateMeRequest
      • User
      • Address
      • GeoPoint
      • D1Region
      • Usage
      • UsageReport
      • Resource
      • Database
      • DataStore
      • NewDatabase
      • NewDataStore
      • QueryRequest
      • DatabasePrivilege
      • ApiKey
      • DbUser
      • Access
      • AccessRequest
      • DatabaseObject
      • NewDatabaseObject
      • NewMigration
      • SchemaOperation
      • Migration
      • Operation
      • Session
      • AdminPowers
      • Admin
      • AuditEntry
      • TeamRole
      • Conversation
      • ChatMessage
      • TeamSso
      • Team
      • TeamMember
      • SshKey
      • ConnectionInfo
      • InboxAddress
      • InboxMailbox
      • InboxMessageSummary
      • InboxMessage
      • InboxNote
      • Page
      • Quote
      • Plan
      • ApiError
      • CapabilityRefusal
      • KlockErrorCode
      • PageWindow
      • SessionView
      • KlockStepUpRequest
      • KlockOpenRequest
      • KlockOpenedSession
      • UpdateMeResult
      • CapabilitiesView
      • SessionLimits
      • Device
      • DeviceListed
      • DeviceTeamRef
      • DeviceCommand
      • DeviceAuditLine
      • DeviceActionRequest
      • StaffActionRequest
      • ManagedSession
      • SessionRevoked
      • AccessRule
      • AccessRuleRequest
      • BehaviourProfile
      • BehaviourProfileRequest
      • BehaviourProfileSaved
      • BehaviourFinding
      • BehaviourFindingAck
      • StepUpProof
      • Removed
      • MemberLockdownRequest
      • McpClient
      • McpDelegatedView
      • McpToolCall
      • McpForwardRequest
      • PasswordlessScope
      • RoleScope
      • PasswordlessSession
      • PasswordlessTlsMaterial
      • PasswordlessKerberosMaterial
      • ServiceDeviceKeys
      • ServiceSession
      • DatabaseRole
      • TransferEndpoint
      • TransferJobRequest
      • TransferQuote
      • TransferStrategy
      • TransferJob
      • TransferJobAccess
      • Pool
      • PoolAllowance
      • BillingSubscription
      • Invoice
      • BillingContact
      • PaymentMethod
      • UpcomingCharges
      • TeamBilling
      • TeamKerberosRealm
      • TeamSsoDomain
      • TeamSsoResponse
      • StoreConnection
      • BatchFailure
      • ProxyStatus
  1. dialects

SingleStore Dialect

Overview#

Reference documentation for the singlestore dialect.
PropertyValue
Dialect namesinglestore
ExtendsMySQLDialect (mysql)
Drivermysql2
Cloud SDKnone
Default port3306
Local runtimeself-hosted; no image in this repo
Source: singlestore
Tests: singlestore, singlestore-crud
Base: mysql

SingleStore (formerly MemSQL) is a distributed, MySQL-wire-compatible database. Because it speaks the MySQL protocol, SingleStoreDialect extends MySQLDialect and reuses the exact same mysql2 driver, connection pooling, query execution, escaping, and the WHERE / ORDER / INSERT / UPDATE / DELETE / SELECT builders. Only the grammar that genuinely differs from stock MySQL is overridden.
Concretely, the dialect:
reports name === 'singlestore' but keeps library === 'mysql2' (verified in tests: dialect.name is 'singlestore', dialect.library is 'mysql2');
defaults the SQL port to 3306 — the constructor calls super({ port: 3306, ...config }), so the MySQL wire port is used unless you override it;
overrides only: CREATE TABLE grammar (storage kind, SHARD KEY, SORT KEY, clustered columnstore key, reference tables), the upsert form, the GEOGRAPHY type mapping, and the foreign-key handling.
SingleStoreDialectOptions is declared as interface SingleStoreDialectOptions extends MySQLDialectOptions {} — the connection options are identical to MySQL's, since the wire protocol and driver are shared.

Quick start#

Install#

$ npm install ts-prorm-orm mysql2
$ pnpm add ts-prorm-orm mysql2
$ yarn add ts-prorm-orm mysql2
$ bun add ts-prorm-orm mysql2
mysql2 is the same driver the mysql dialect uses.

Connect#

import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'singlestore',
  host: 'svc-abc.svc.singlestore.com',
  database: 'app',
  username: 'admin',
  password: process.env.DB_PASSWORD,
});
import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'singlestore',
  url: 'singlestore://admin:secret@svc-abc.svc.singlestore.com:3306/app',
});
A URL is folded into host, port, database, username and password before the dialect is built; any of those passed alongside it wins.

Define a model#

import { DataTypes } from 'ts-prorm-orm';

const User = db.define('User', {
  id: { type: DataTypes.INTEGER(), primaryKey: true, autoIncrement: true },
  email: { type: DataTypes.STRING(255), allowNull: false, unique: true },
  name: { type: DataTypes.STRING(100) },
});

await db.sync(); // CREATE TABLE — see Generated SQL below

Query#

import { Op } from 'ts-prorm-orm';

await User.create({ email: 'ada@example.com', name: 'Ada' });

const page = await User.findAll({
  where: { name: { [Op.like]: 'A%' } },
  order: [['id', 'ASC']],
  limit: 20,
  offset: 40,
});

Generated SQL#

Each block is the statement the model call above it hands the dialect's query(), captured with the driver stubbed out. The model layer inlines the values.

Create table#

db.sync() for the model in the Quick start:
CREATE TABLE

Insert, update and delete#

await User.create({ email: 'ada@example.com', name: 'Ada' });
await User.update({ name: 'Grace' }, { where: { email: 'ada@example.com' } });
await User.destroy({ where: { id: 1 } });

Upsert#

await User.upsert({ id: 1, email: 'ada@example.com', name: 'Ada Lovelace' });
upsert() also reads the row by primary key before and after the write, to return the instance.

Pagination#

await User.findAll({
  where: { name: { [Op.like]: 'A%' } },
  order: [['id', 'ASC']],
  limit: 20,
  offset: 40,
});

JSON#

[!NOTE] No JSON operator in the WHERE builder
DataTypes.JSON() maps to JSON, but this dialect's WHERE builder refuses Op.contains on it: Cannot render WHERE condition at meta.contains' is not implemented by its WHERE builder. The statement was not sent, because running it without the condition would match rows it should not.

Transaction#

await db.transaction(async (t) => {
  await User.create({ email: 'grace@example.com', name: 'Grace' }, { transaction: t });
  await User.update({ name: 'Grace Hopper' }, { where: { email: 'grace@example.com' }, transaction: t });
});
[!WARNING] No savepoints
Nested transactions need savepoints, and singlestore has none. Run the work in a single transaction, or restructure it so nothing nests.
Type mapping for the portable descriptors: STRING → VARCHAR(255), auto-increment INTEGER → INT, BOOLEAN → TINYINT(1), DATE → DATETIME, UUID → CHAR(36), JSON → JSON. The type comparison lines the major engines up side by side.

Connection#

import { Prorm } from 'ts-prorm-orm';

const prorm = new Prorm({
  dialect: 'singlestore',
  host: 'your-singlestore-host',
  port: 3306, // default; SingleStore uses the MySQL wire protocol
  database: 'app',
  username: 'admin',
  password: 'secret',
});

await prorm.connect();
'singlestore' is a registered dialect string in Prorm.createDialect; it is lazy-loaded (require('./dialects/singlestore').SingleStoreDialect) so the mysql2 driver is only required when the dialect is actually used. If port is omitted, the dialect constructor supplies 3306.

3. SingleStore-specific features#

These are configured through SingleStoreTableOptions, which is intersected with the shared TableOptions and passed to createTable(...) / buildCreateTableSQL(...):
interface SingleStoreTableOptions {
  rowstore?: boolean;                    // CREATE ROWSTORE TABLE ...
  reference?: boolean;                   // CREATE REFERENCE TABLE ...
  shardKey?: string[];                   // SHARD KEY (...)  ([] => SHARD KEY ())
  sortKey?: string[];                    // SORT KEY (...)
  columnstoreKey?: { fields: string[] }; // KEY (...) USING CLUSTERED COLUMNSTORE
}
buildCreateTableSQL(tableName, columns, options) is a synchronous, no-I/O builder (so the grammar can be inspected/tested without a live connection); createTable(...) delegates to it and then creates any secondary indexes.

SHARD KEY and SORT KEY (columnstore)#

SingleStore is distributed and shards data across leaf nodes by a shard key; columnstore tables also store rows ordered by a sort key.
dialect.buildCreateTableSQL(
  'events',
  {
    id: { type: DataTypes.BIGINT, allowNull: false },
    user_id: { type: DataTypes.BIGINT, allowNull: false },
    created_at: { type: DataTypes.DATE },
  },
  { shardKey: ['user_id'], sortKey: ['created_at'] },
);
Emits (columnstore is the default — no ROWSTORE/REFERENCE keyword):
(Tests assert the output contains CREATE TABLE `events`, SHARD KEY (`user_id`), and SORT KEY (`created_at`). DATE maps to DATETIME — see the type table.)

Keyless SHARD KEY (random sharding)#

An empty shardKey array emits the keyless SHARD KEY () form, which requests random sharding (also how a plain distributed table with no explicit shard key is declared). Note shardKey is emitted whenever it is not undefined, so [] still produces a clause:
dialect.buildCreateTableSQL(
  'metrics',
  { value: { type: DataTypes.DOUBLE } },
  { shardKey: [] },
);

ROWSTORE tables#

SingleStore tables are columnstore by default. { rowstore: true } requests an in-memory rowstore table:
dialect.buildCreateTableSQL(
  'sessions',
  { id: { type: DataTypes.BIGINT, primaryKey: true } },
  { rowstore: true, shardKey: ['id'] },
);

REFERENCE (replicated) tables#

{ reference: true } emits CREATE REFERENCE TABLE. Reference tables are fully replicated to every node rather than sharded — typically small dimension tables joined against large sharded fact tables (so a shard key is normally omitted):
dialect.buildCreateTableSQL(
  'countries',
  {
    code: { type: DataTypes.STRING, primaryKey: true },
    name: { type: DataTypes.STRING },
  },
  { reference: true },
);

USING CLUSTERED COLUMNSTORE key#

{ columnstoreKey: { fields: [...] } } emits the explicit clustered-columnstore key form. It is only emitted when fields is non-empty:
dialect.buildCreateTableSQL(
  'logs',
  {
    ts: { type: DataTypes.DATE },
    message: { type: DataTypes.TEXT },
  },
  { columnstoreKey: { fields: ['ts'] } },
);

Clause ordering#

Within the parenthesised body, buildCreateTableSQL appends parts in this order: column definitions → table constraints (PK/UNIQUE/CHECK) → SHARD KEY (...) → SORT KEY (...) → KEY (...) USING CLUSTERED COLUMNSTORE. Table-level options (DEFAULT CHARSET=, COLLATE, COMMENT=, and IF NOT EXISTS) are inherited-style and handled after the body.

4. Caveats#

Foreign keys are not supported — the dialect refuses to emit FK SQL#

SingleStore does not support foreign key constraints (a real server rejects FOREIGN KEY ... REFERENCES ...). Rather than generate statements that would fail, the dialect handles FKs as follows:
CREATE TABLE, table-level FOREIGN KEY constraint — silently omitted. The private buildTableConstraintSQL returns null for FOREIGN KEY (PRIMARY KEY / UNIQUE / CHECK are emitted normally), so the table is still created, just without the FK clause. A test passes a FOREIGN KEY constraint and asserts the output contains neither FOREIGN KEY nor REFERENCES.
CREATE TABLE, column-level references — also omitted. buildColumnSQL never emits a REFERENCES clause, so a column definition carrying references produces no REFERENCES in the DDL (verified by test).
addColumn / changeColumn — strip any column-level references (via stripReferences) before delegating to the MySQL base, whose column builder would otherwise emit a REFERENCES ... clause SingleStore rejects.
addForeignKey(...) — throws: SingleStore does not support foreign key constraints. Enforce referential integrity in application code instead.
createConstraint(...) with type: 'FOREIGN KEY' — throws the same error. Other constraint types delegate to the MySQL base.
Enforce referential integrity in application code instead.

Unique constraints on columnstore tables must include the shard key#

This is a SingleStore data-distribution rule (a unique index on a columnstore table must contain the shard key columns). As documented in the source header, the ORM does not attempt to police this — it will emit the UNIQUE (...) you ask for; a real server enforces the rule. Plan your UNIQUE constraints/shardKey accordingly.

No RETURNING clause#

Like MySQL, SingleStore has no RETURNING clause. buildUpsertQuery(..., { returning: true }) fails fast with an error matching /RETURNING/; re-fetch the row after the upsert instead.

5. Inherited MySQL behavior#

CRUD and standard DDL are inherited from MySQLDialect and behave identically, using backtick identifier quoting and ? placeholders. Verified in the CRUD tests:
INSERT
dialect.buildInsertQuery('users', { id: 1, name: 'Ada' });
// sql:    INSERT INTO `users` (`id`, `name`) VALUES (?, ?)
// values: [1, 'Ada']
Literal values are inlined without a placeholder:
dialect.buildInsertQuery('t', { id: 1, created_at: new Literal('NOW()') });
// sql:    INSERT INTO `t` (`id`, `created_at`) VALUES (?, NOW())
// values: [1]
UPDATE / DELETE / INCREMENT
dialect.buildUpdateQuery('users', { name: 'Grace' }, { id: 1 }, { limit: 1 });
// UPDATE `users` SET `name` = ? WHERE `id` = ? LIMIT 1   values: ['Grace', 1]

dialect.buildDeleteQuery('users', { id: 7 });
// DELETE FROM `users` WHERE `id` = ?                     values: [7]

dialect.buildIncrementQuery('posts', 'views', { id: 3 }, { by: 2 });
// UPDATE `posts` SET `views` = `views` + ? ...           values: [2, 3]
SELECT — inherited WHERE (AND / Op.or), ORDER BY, GROUP BY / HAVING, and LIMIT/OFFSET. MySQL's offset-only semantics are preserved: buildLimitOffset(undefined, 10) yields LIMIT 18446744073709551615 OFFSET 10.
Standard DDL — IF NOT EXISTS, DEFAULT CHARSET=, COLLATE, and table COMMENT= all work through buildCreateTableSQL:
PRIMARY KEY / UNIQUE / CHECK table constraints emit normally alongside a shard key:

Upsert: ON DUPLICATE KEY UPDATE with the VALUES(col) form#

This is the one CRUD override. The MySQL base emits the MySQL 8.0.19 row-alias form (... AS new_vals ... = new_vals.col), which SingleStore does not support. SingleStoreDialect overrides both buildInsertQuery (upsert branch) and buildUpsertQuery to emit the classic VALUES(col) reference instead:
dialect.buildInsertQuery(
  'users',
  { id: 1, name: 'Ada', email: 'ada@x.io' },
  { upsert: true },
);
// ... ON DUPLICATE KEY UPDATE `id` = VALUES(`id`), `name` = VALUES(`name`), `email` = VALUES(`email`)
// (never contains "AS new_vals" or "new_vals.")
updateOnDuplicate restricts the SET list; otherwise all inserted columns are updated:
dialect.buildUpsertQuery('kv', { k: 'a', v: 10 });
// INSERT INTO `kv` (`k`, `v`) VALUES (?, ?) ON DUPLICATE KEY UPDATE `k` = VALUES(`k`), `v` = VALUES(`v`)
// values: ['a', 10]

6. Type mapping#

Scalar types are mapped exactly as in MySQL (getDataTypeSql calls super.getDataTypeSql) — with one override: the geospatial GEOGRAPHY type. SingleStore has a native GEOGRAPHY type, whereas stock MySQL has none and the base dialect degrades it to GEOMETRY. The dialect intercepts { key: 'GEOGRAPHY' } and returns the native type so geography columns round-trip correctly.
ORM type (DataTypes.* / { key })SingleStore SQLNotes
STRINGVARCHAR(255)inherited from MySQL
BIGINTBIGINTinherited
INTEGERINTinherited
DOUBLEDOUBLEinherited
BOOLEANTINYINT(1)inherited
JSONJSONinherited
DATEDATETIMEinherited
UUIDCHAR(36)inherited
TEXTTEXTinherited
DECIMAL (precision 10, scale 2)DECIMAL(10,2)inherited
GEOMETRYGEOMETRYinherited (unchanged)
GEOGRAPHYGEOGRAPHYSingleStore override (MySQL base would emit GEOMETRY)
All rows except GEOGRAPHY are asserted directly in the type-mapping tests; the GEOGRAPHY override and the GEOMETRY contrast are also asserted.
The source header also mentions GEOGRAPHYPOINT as a SingleStore native type, but only the GEOGRAPHY key is intercepted in getDataTypeSql; there is no dedicated GEOGRAPHYPOINT mapping in the code.

7. Not yet verified against a live server#

Everything above about SQL string generation is verified by the unit tests, which exercise only the synchronous builders (buildCreateTableSQL, buildInsertQuery, buildUpsertQuery, buildSelectQuery, buildUpdateQuery, buildDeleteQuery, buildIncrementQuery, getDataTypeSql, buildLimitOffset) plus the FK-rejection error paths. No test opens a connection (connect() is never called).
The following are not exercised against a real SingleStore instance and should be validated in a live environment before relying on them:
Connectivity and the mysql2 driver against a real cluster — pool creation, authentication, retries, and query execution are inherited from the MySQL dialect and untested here against SingleStore specifically.
Server acceptance of the generated DDL — that a live SingleStore server accepts SHARD KEY, SORT KEY, KEY (...) USING CLUSTERED COLUMNSTORE, CREATE ROWSTORE TABLE, and CREATE REFERENCE TABLE exactly as emitted.
Data-distribution rules — that a UNIQUE constraint including the shard key is accepted, and that one omitting it is rejected by the server (the ORM does not police this).
Runtime behavior of VALUES(col) upserts, GEOGRAPHY round-tripping, and the FK omission — that omitting foreign keys behaves acceptably for your integrity needs, and that the columnstore/rowstore/reference semantics match expectations at query time.
Introspection helpers inherited from MySQL (showTables, describeTable, getCreateTable, showIndexes, showConstraints, INFORMATION_SCHEMA-based partition helpers, etc.) — these assume MySQL system-catalog shapes and have not been checked against SingleStore.

What differs from MySQL#

SingleStoreDialect extends MySQLDialect (mysql) and
overrides 23 of its methods (Object.getOwnPropertyNames(SingleStoreDialect.prototype),
computed by the scratch test); everything else is inherited unchanged.
AreaOverridden
DML buildersbuildInsertQuery, buildUpsertQuery, formatDefaultValue
TypeslegacyDataTypeSql, mapNativeType, modernDataTypeSql
DDL and schemaaddColumn, addForeignKey, buildColumnSQL, buildCreateTableSQL, buildTableConstraintSQL, changeColumn, createConstraint, createSavepointSQL, createTable, createTrigger, dropTrigger
IntrospectionhasTrigger, listTriggers
OtherlegacyNeedsModern, releaseSavepointSQL, rollbackToSavepointSQL, stripReferences

Capabilities#

Computed from the code — capabilitiesOf() (src/transaction-support.ts),
whereSupportOf() (src/query-builders/expression-render.ts),
sqlObjectCapabilitiesOf() (src/sql-objects/capabilities.ts) and the
builders — by the scratch test described in the
capability matrix.
Capabilitysinglestore
Transactions atomicyes
Savepointsno — a nested transaction() throws
Isolationup to SERIALIZABLE
Transaction modesread-only yes; deferrable no; constraint deferral no
RETURNINGnot emitted; returning is accepted and ignored
UpsertINSERT … ON DUPLICATE KEY UPDATE
JSON columnJSON (JSONB → JSON)
Vector columnVECTOR(3, F32)
Array columnVARCHAR(255)
WHERE builder28 operator keys plus the $json: prefix; $and/$or/$not; $exists: no; $in subquery: no; expression operands: no
SQL objectsfamily mysql: triggers yes; procedures yes; functions multiStatement; materialized views emulated (procedure); sequences no; enums inline; RLS no
StreamingqueryStream() present; LISTEN absent; createExtension() present

Testing#

tests/dialects/singlestore.test.ts exercises the dialect with a mocked driver, so nothing touches a server.

Related reading#

All dialects — what each engine supports
Data types — how each type maps to this engine
Querying — how a FindOptions becomes SQL
Modified at 2026-10-04 00:40:16
Previous
rqlite Dialect
Next
Snowflake Dialect
Built with