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

MySQL Dialect

The MySQL dialect targets MySQL 5.7 and 8.0+ servers (and compatible forks). It is
implemented in mysql on
top of the mysql2 driver, using its
promise API and a connection pool.

Overview#

Dialect name: mysql
Underlying library: mysql2 (mysql2/promise)
Identifier quoting: backticks — `table`.`column`
Placeholders: positional ?
Pooling: always on (mysql.createPool), sized from pool.max (default 10)
Upsert: INSERT ... ON DUPLICATE KEY UPDATE
Auto-increment: AUTO_INCREMENT columns + LAST_INSERT_ID()
Full-text search: MATCH(...) AGAINST(...) over FULLTEXT indexes
PropertyValue
Dialect namemysql
Extendsnothing — implements Dialect directly
Drivermysql2
Cloud SDKnone
Default port3306
Local runtimeprorm db up --dialect mysql (mysql:8.0.39); docker-compose.test.yml
MySQL organizes objects into databases, not schemas. Schema-oriented methods
(createSchema, dropSchema, showAllSchemas) intentionally throw and point you at
the CREATE DATABASE / DROP DATABASE / SHOW DATABASES equivalents;
listSchemas() runs SHOW DATABASES.

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

Connect#

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

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

export const db = new Prorm({
  dialect: 'mysql',
  url: 'mysql://app:secret@localhost: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 with a savepoint#

await db.transaction(async (t) => {
  await User.create({ email: 'grace@example.com', name: 'Grace' }, { transaction: t });
  // A nested transaction is a SAVEPOINT; its failure undoes only its own work.
  await db
    .transaction(async (sp) => {
      await User.destroy({ where: { id: 1 }, transaction: sp });
      throw new Error('keep the row');
    }, { transaction: t })
    .catch(() => {});
});

Skip locked rows (SKIP LOCKED)#

A worker that claims rows from a queue table should pass over rows another transaction holds rather than wait for them. lock with skipLocked inside a transaction:
await db.transaction(async (t) => {
  await User.findAll({ where: { name: 'Ada' }, lock: { level: 'UPDATE', skipLocked: true }, transaction: t });
});
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#

Pass dialect: 'mysql' to the Prorm constructor along with standard connection
fields. The default host is localhost and the default port is 3306.
import { Prorm } from 'ts-prorm-orm';

const db = new Prorm({
  dialect: 'mysql',
  host: '127.0.0.1',
  port: 3306,
  username: 'app',
  password: 's3cret',
  database: 'shop',
});

await db.connect();      // creates the pool and verifies one connection
// ... use the database ...
await db.close();        // pool.end()
You can also construct the dialect directly when you only need the query builder /
raw execution surface:
import { createMySQLDialect } from 'prorm/dialects/mysql';

const dialect = createMySQLDialect({
  host: '127.0.0.1',
  port: 3306,
  username: 'app',
  password: 's3cret',
  database: 'shop',
  charset: 'utf8mb4',   // default
  timezone: 'Z',        // default — store/read as UTC
  pool: { max: 20 },    // maps to mysql2 connectionLimit
});

await dialect.connect();
const version = await dialect.getDatabaseVersion(); // SELECT VERSION()

Connection options#

OptionDefaultNotes
hostlocalhost
port3306
username / password / database—Passed to mysql2 as user / password / database.
charsetutf8mb4Full Unicode incl. emoji.
timezoneZUTC.
ssl—Passed straight through to mysql2.
pool{ max: 10 }pool.max sets the mysql2 connectionLimit.
retrysee belowConnection/query retry policy.
connectTimeout / idleTimeout—Forwarded to mysql2 when set.
Both connect() and query() retry on transient failures (ECONNREFUSED,
ETIMEDOUT, Too many connections, Lock wait timeout, deadlocks, etc.). By
default up to 3 attempts with a fixed 1s delay plus jitter; enable
retry.backoff for exponential backoff.

Placeholders#

MySQL uses positional ? placeholders, and the builder methods emit them.
Values travel out-of-band in the values array — never string-interpolate user
input.
const { sql, values } = dialect.buildInsertQuery('users', {
  email: 'ada@example.com',
  name: 'Ada',
});
// sql:    INSERT INTO `users` (`email`, `name`) VALUES (?, ?)
// values: ['ada@example.com', 'Ada']

await dialect.query(sql, { replacements: values });
Raw SQL fragments can be embedded with a Literal, which is inlined verbatim
(and therefore not escaped) instead of becoming a ?:
// `Literal` lives in src/core/expressions and is not exported from the package root.
import { Literal } from 'ts-prorm-orm/core/expressions';

dialect.buildInsertQuery('events', { name: 'signup', at: new Literal('NOW()') });
// INSERT INTO `events` (`name`, `at`) VALUES (?, NOW())

Data types#

getDataTypeSql() maps the ORM's DataTypes to MySQL column types:
ORM typeMySQL column
STRING(n)VARCHAR(n) (default 255)
CHAR(n)CHAR(n)
TEXTTEXT / MEDIUMTEXT / LONGTEXT (by length)
INTEGERINT (or TINYINT / SMALLINT / MEDIUMINT / BIGINT by length), UNSIGNED supported
BIGINTBIGINT
FLOAT / DOUBLE / DECIMAL(p,s)FLOAT / DOUBLE / DECIMAL(p,s)
BOOLEANTINYINT(1)
DATEDATETIME (DATETIME(p) with precision)
DATEONLY / TIMEDATE / TIME
BLOBBLOB (TINYBLOB / MEDIUMBLOB / LONGBLOB)
ENUM / SETENUM(...) / SET(...)
JSON / JSONBJSON (MySQL has no separate JSONB)
UUIDCHAR(36)
BIT / YEARBIT(n) / YEAR
GEOMETRY, POINT, POLYGON, ...native spatial types, optional SRID
BOOLEAN is stored as TINYINT(1); booleans are emitted as the TRUE / FALSE
keywords (not 1 / 0) so comparisons against JSON booleans extracted with
JSON_EXTRACT() behave correctly.

Creating tables and AUTO_INCREMENT#

AUTO_INCREMENT is the MySQL identity mechanism. Mark a column
autoIncrement: true (typically with primaryKey: true); after an insert,
LAST_INSERT_ID() returns the generated value.
await dialect.createTable(
  'users',
  {
    id:    { type: 'BIGINT', primaryKey: true, autoIncrement: true },
    email: { type: 'VARCHAR(255)', allowNull: false, unique: true },
    name:  { type: 'VARCHAR(120)' },
    bio:   { type: 'TEXT' },
    created_at: { type: 'DATETIME', defaultValue: 'CURRENT_TIMESTAMP' },
  },
  {
    engine: 'InnoDB',
    charset: 'utf8mb4',
    initialAutoIncrement: 1000,   // AUTO_INCREMENT=1000
  },
);

const res = await dialect.query(
  'INSERT INTO `users` (`email`, `name`) VALUES (?, ?)',
  { replacements: ['ada@example.com', 'Ada'] },
);
// res.rowCount === affectedRows

const [{ id }] = (
  await dialect.query('SELECT LAST_INSERT_ID() AS id')
).rows;
Table options include engine, charset, collate, comment,
initialAutoIncrement, and rowFormat. Column definitions support
CHARACTER SET / COLLATE, INVISIBLE columns (MySQL 8.0+), and comments.
A column's references (and an association's onDelete / onUpdate) is
declared as a table-level FOREIGN KEY (…) REFERENCES … ON DELETE …, in
CREATE TABLE and ADD COLUMN, because InnoDB ignores a column-level
REFERENCES. Before 4.9.2 the column-level form was emitted and no foreign
key was created; the same applies to MariaDB and TiDB.

Upsert: ON DUPLICATE KEY UPDATE#

MySQL's upsert is INSERT ... ON DUPLICATE KEY UPDATE. It fires whenever a row
would violate any PRIMARY KEY or UNIQUE constraint — you cannot scope it to
a specific set of conflict columns the way PostgreSQL's ON CONFLICT (cols) does.
The builder uses the row-alias form (AS new_vals) rather than the deprecated
VALUES(col) function form removed in newer MySQL:
const { sql, values } = dialect.buildUpsertQuery(
  'users',
  { email: 'ada@example.com', name: 'Ada Lovelace', login_count: 1 },
  { updateOnDuplicate: ['name', 'login_count'] },
);
// INSERT INTO `users` (`email`, `name`, `login_count`)
//   VALUES (?, ?, ?) AS new_vals
//   ON DUPLICATE KEY UPDATE `name` = new_vals.`name`,
//                           `login_count` = new_vals.`login_count`

await dialect.query(sql, { replacements: values });
If updateOnDuplicate is omitted, every inserted column is updated on conflict.
buildInsertQuery(..., { upsert: true }) produces the same clause inline.
RETURNING is not supported. MySQL has no RETURNING clause, so passing
returning to buildUpsertQuery throws rather than emitting invalid SQL.
Re-select the row afterward (e.g. via LAST_INSERT_ID() or the known unique
key).

Full-text search: MATCH ... AGAINST#

Create a FULLTEXT index, then query it with MATCH(...) AGAINST(...). Full-text
indexes require InnoDB or MyISAM and only apply to CHAR / VARCHAR / TEXT
columns.
await dialect.createFulltextIndex('articles', 'ft_body', ['title', 'body']);

// Build a MATCH expression directly:
const expr = dialect.buildMatchAgainst(['title', 'body'], 'search engines', {
  mode: 'boolean',
});
// MATCH(`title`, `body`) AGAINST('search engines' IN BOOLEAN MODE)

const { rows } = await dialect.query(
  `SELECT id, title FROM \`articles\` WHERE ${expr} LIMIT 20`,
);
buildMatchAgainst supports mode: 'natural' (default, IN NATURAL LANGUAGE MODE) and mode: 'boolean' (IN BOOLEAN MODE), plus query-expansion modifiers.
In WHERE objects the $match operator produces a parameterized MATCH(...) AGAINST(? ...) predicate:
const { sql, values } = dialect.buildWhereClause({
  body: { $match: { columns: ['title', 'body'], searchTerm: 'ada', mode: 'boolean' } },
});
// sql:    MATCH(`title`, `body`) AGAINST(? IN BOOLEAN MODE)
// values: ['ada']

Querying, bulk insert and JSON#

query() returns { rows, rowCount, fields }. SELECT / SHOW / DESCRIBE /
EXPLAIN populate rows; other statements report affectedRows as rowCount.
For large result sets, queryStream() returns a Node Readable backed by
mysql2's streaming API. bulkInsert() batches many rows into one multi-row
INSERT:
await dialect.bulkInsert('users', [
  { email: 'a@example.com', name: 'A' },
  { email: 'b@example.com', name: 'B' },
]);
// INSERT INTO `users` (`email`, `name`) VALUES (?, ?), (?, ?)
MySQL's JSON type is well supported via helpers such as buildJsonExtract
(JSON_UNQUOTE(JSON_EXTRACT(...))), buildJsonContains, buildJsonSet,
buildJsonTable (8.0+), and the JSON_ARRAYAGG / JSON_OBJECTAGG aggregates.
OFFSET without LIMIT is emitted as LIMIT 18446744073709551615 OFFSET n,
since MySQL requires a LIMIT alongside OFFSET.

Transactions and savepoints#

MySQLTransaction wraps a dedicated pooled connection and supports
commit() / rollback() plus nested SAVEPOINT operations
(createSavepoint, rollbackToSavepoint, releaseSavepoint).
const tx = await db.transaction();
try {
  const sp = await tx.createSavepoint();
  // ... work on tx.connection ...
  await tx.releaseSavepoint(sp);
  await tx.commit();
} catch (err) {
  await tx.rollback();
  throw err;
}

Partitioning#

MySQL supports RANGE, LIST, HASH, and KEY partitioning declared in
CREATE TABLE. createPartitionedTable emits RANGE COLUMNS / LIST COLUMNS
so non-integer partition columns (dates, strings) work, and addPartition /
dropPartition manage partitions on an existing table. dropPartition will look
up the parent table from INFORMATION_SCHEMA.PARTITIONS if you don't pass
parentTable.

Limitations#

No schemas. MySQL uses databases; the schema methods throw with guidance
toward CREATE DATABASE / SHOW DATABASES.
No RETURNING. Re-fetch after insert/upsert (LAST_INSERT_ID()).
No DETACH PARTITION. detachPartition throws; use DROP PARTITION.
No Foreign Data Wrappers. createUserMapping / dropUserMapping and
related FDW methods throw (PostgreSQL-only features).
Upsert conflict scope. ON DUPLICATE KEY UPDATE reacts to any unique-key
collision and cannot be limited to specific conflict columns.
JSONB maps to JSON. MySQL has a single native JSON type.
For a MySQL-compatible distributed database, see the TiDB dialect, which shares
much of this SQL surface.

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.
Capabilitymysql
Transactions atomicyes
Savepointsyes
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)
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

Related reading#

Running mysql in Docker — get one going locally
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
Microsoft SQL Server Dialect
Next
Neon Dialect
Built with