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

MariaDB Dialect

The MariaDB dialect provides first-class support for MariaDB servers. It shares
most of its SQL surface with the MySQL dialect (backtick identifiers, the
mariadb npm driver's pooled connections, ON DUPLICATE KEY UPDATE upserts) but
diverges where MariaDB has grown its own features: native RETURNING clauses,
sequences, virtual columns, system-versioned tables, and the CONNECT storage
engine.
Source: mariadb.

Overview#

Dialect name: mariadb
Driver: mariadb (the official
MariaDB Connector/Node.js). Install it alongside the ORM.
Identifier quoting: backticks (`column`), same as MySQL.
Default storage engine: InnoDB. createTable emits ENGINE=InnoDB
unless you override it via the engine table option.
Status: Stable.
PropertyValue
Dialect namemariadb
Extendsnothing — implements Dialect directly
Drivermariadb
Cloud SDKnone
Default port3306
Local runtimeprorm db up --dialect mariadb (mariadb:11.4.3); docker-compose.test.yml
MariaDB started as a MySQL fork, so anything you know from the MySQL dialect
generally applies. The sections below focus on where MariaDB is either a strict
superset of MySQL or behaves differently.

Quick start#

Install#

$ npm install ts-prorm-orm mariadb
$ pnpm add ts-prorm-orm mariadb
$ yarn add ts-prorm-orm mariadb
$ bun add ts-prorm-orm mariadb

Connect#

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

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

export const db = new Prorm({
  dialect: 'mariadb',
  url: 'mariadb://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) },
  meta: { type: DataTypes.JSON() },
});

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#

Containment on the meta column:
import { Op } from 'ts-prorm-orm';

await User.findAll({ where: { meta: { [Op.contains]: { plan: 'pro' } } } });

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 → BOOLEAN, DATE → DATETIME, UUID → CHAR(36), JSON → JSON. The type comparison lines the major engines up side by side.

Connection#

Pass dialect: 'mariadb' to the Prorm constructor along with standard
connection fields. The dialect defaults host to localhost and port to
3306, and creates a connection pool via mariadb.createPool under the hood.
import { Prorm, DataTypes } from 'ts-prorm-orm';

const prorm = new Prorm({
  dialect: 'mariadb',
  host: 'localhost',
  port: 3306,
  database: 'app',
  username: 'root',
  password: 'password',
});

await prorm.connect(); // opens the pool and authenticates

Connection options#

The dialect accepts these options (see MariaDBDialectOptions):
OptionDefaultNotes
hostlocalhostServer hostname.
port3306Server port.
database—Default schema.
username—Mapped to the driver's user field.
password—Password.
charsetutf8mb4Connection charset.
timezoneZPool normalizes to UTC; date binding uses UTC accordingly.
ssl—Passed straight to the driver.
connectionLimit10Max pooled connections.
waitForConnectionstrueQueue requests when the pool is saturated.
queueLimit00 means an unbounded queue.
insertIdAsNumbertrueReturn insertId as a JS number.
decimalAsFloatfalseKeep DECIMAL precise instead of coercing to float.
debug / tracefalseDriver-level diagnostics.
Because the pool is configured with supportBigNumbers: true and
timezone: 'Z', BIGINT values are preserved and Date values are stored and
read as UTC. If you supply Date objects, the dialect formats them with UTC
getters so what you insert matches what the server stores.
const prorm = new Prorm({
  dialect: 'mariadb',
  host: 'db.internal',
  database: 'app',
  username: 'app_rw',
  password: process.env.DB_PASSWORD,
  dialectOptions: {
    connectionLimit: 20,
    ssl: { rejectUnauthorized: true },
  },
});

How MariaDB differs from MySQL#

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

Like MySQL, MariaDB implements upserts with INSERT ... ON DUPLICATE KEY UPDATE.
buildInsertQuery (with upsert: true) and buildUpsertQuery both emit the
VALUES(col) form to reference the would-be-inserted value in the update clause:
Note: VALUES(col) in the ON DUPLICATE KEY UPDATE clause is the classic MySQL
and MariaDB syntax. MariaDB has never adopted the MySQL 8.0.19 AS new
row-alias replacement, so VALUES(col) remains the portable, correct form for
MariaDB — which is exactly what this dialect generates.
At the model layer, use upsert. It returns [instance, created]:
const User = prorm.define('User', {
  id: { type: DataTypes.INTEGER, primaryKey: true, autoIncrement: true },
  name: DataTypes.STRING(100),
  email: { type: DataTypes.STRING(255), unique: true },
});

await prorm.sync();

// Update only `name` when a row with the same key already exists.
const [user, created] = await User.upsert(
  { id: 1, name: 'Ada', email: 'ada@example.com' },
  { updateOnDuplicate: ['name'] },
);
console.log(created ? 'inserted' : 'updated', user.toJSON());
If you omit updateOnDuplicate, every supplied column is written into the
ON DUPLICATE KEY UPDATE clause.

RETURNING support#

This is the headline difference from MySQL. MySQL has no RETURNING clause;
MariaDB does.
The dialect emits RETURNING for INSERT, UPDATE, and
DELETE when you pass a returning option:
returning: true renders RETURNING * on INSERT/UPDATE/DELETE (upserts expand
it to the explicit column list).
returning: ['id', 'name'] renders RETURNING \id`, `name``.
// buildInsertQuery(..., { returning: true }) produces:
//   INSERT INTO `users` (`name`, `email`) VALUES (?, ?) RETURNING *
//
// buildDeleteQuery(..., { returning: ['id'] }) produces:
//   DELETE FROM `users` WHERE `id` = ? RETURNING `id`
Version caveats (be honest about the server you run against):
INSERT ... RETURNING requires MariaDB 10.5+.
DELETE ... RETURNING has been available since MariaDB 10.0.5.
UPDATE ... RETURNING is not supported by MariaDB at all. The dialect's
buildUpdateQuery will still append the clause if you pass returning, but the
server rejects it. Treat returning on updates as unsupported and read the row
back with a follow-up SELECT instead.
The dialect always emits the clause when you ask for it; it does not gate on the
server version. Only rely on it for INSERT (10.5+) and DELETE (10.0.5+).

Sequences#

MariaDB 10.0+ has real CREATE SEQUENCE objects (MySQL does not). The dialect's
createSequence / dropSequence emit standard sequence DDL, and supports
CREATE OR REPLACE SEQUENCE, IF NOT EXISTS, and TEMPORARY sequences.

OFFSET without LIMIT#

Like MySQL, MariaDB cannot use OFFSET without a LIMIT. When only an offset is
given, the dialect supplies the documented max unsigned BIGINT as the limit so
all remaining rows are returned:

Partitions#

MariaDB supports RANGE, LIST, HASH, KEY, and LINEAR partitioning.
Partitions are created inline in CREATE TABLE or added later with
ALTER TABLE ... ADD PARTITION. Note that MariaDB has no DETACH PARTITION
operation — detachPartition throws; use dropPartition (which emits
ALTER TABLE ... DROP PARTITION) instead.

Data types#

getDataTypeSql maps the ORM's DataTypes to MariaDB column types:
DataTypeMariaDB SQL
STRING(n)VARCHAR(n) (default VARCHAR(255))
CHAR(n)CHAR(n)
TEXTTEXT / TINYTEXT / MEDIUMTEXT / LONGTEXT by length
INTEGERTINYINT / SMALLINT / MEDIUMINT / INT / BIGINT by length, UNSIGNED when set
BIGINTBIGINT (UNSIGNED when set)
FLOAT / DOUBLEFLOAT / DOUBLE (optionally (len,decimals))
DECIMALDECIMAL(precision, scale)
BOOLEANBOOLEAN (native)
DATEDATETIME (or DATETIME(precision))
DATEONLYDATE
TIMETIME (or TIME(precision))
BLOBBLOB / TINYBLOB / MEDIUMBLOB / LONGBLOB
ENUM(...)ENUM('a','b',...)
JSON / JSONBJSON (MariaDB 10.2+; stored as LONGTEXT with a JSON check under the hood)
UUIDCHAR(36)
GEOMETRYGEOMETRY

JSON#

MariaDB exposes JSON functions rather than a distinct binary JSON storage type.
The dialect builds them for you:
buildJsonExtract → JSON_UNQUOTE(JSON_EXTRACT(col, '$.path')) for text, or
JSON_EXTRACT(...) when asText is false.
buildJsonContains → JSON_CONTAINS(col, ?, '$.path').
buildJsonHasKey → JSON_CONTAINS_PATH(col, 'one'|'all', '$.key').
buildJsonSet / buildJsonReplace / buildJsonInsert /
buildJsonRemove → the matching JSON_SET / JSON_REPLACE / JSON_INSERT /
JSON_REMOVE functions (MariaDB 10.2.3+).
buildJsonMergePatch → JSON_MERGE_PATCH (RFC 7396) and
buildJsonMergePreserve → JSON_MERGE_PRESERVE (MariaDB 10.2.4+; the dialect
always emits the explicit name rather than the deprecated JSON_MERGE alias).
const preferences = prorm.getDialectInstance();
// SELECT ... WHERE JSON_UNQUOTE(JSON_EXTRACT(`prefs`, '$.theme')) = ?
const expr = preferences.buildJsonExtract('prefs', 'theme');

MariaDB-specific table & column options#

createTable accepts MariaDBTableOptions and columns accept
MariaDBColumnDefinition. Highlights:
engine — storage engine (InnoDB, Aria, MyISAM, MEMORY,
CONNECT, ...). Constants live in MariaDBStorageEngines.
autoIncrement — table-level AUTO_INCREMENT= seed; per-column
autoIncrementInit seeds an individual AUTO_INCREMENT column.
rowFormat, keyBlockSize, tableComment, check.
systemVersioning: true — appends WITH SYSTEM VERSIONING for MariaDB
10.3+ temporal (system-versioned) tables.
connectType / connectOptions — switch the table to the CONNECT
engine and set TYPE= plus OPTIONS(...) for external data sources
(MYSQL, ODBC, CSV, JSON, ...); see MariaDBConnectTypes.
Virtual columns — set generated: 'VIRTUAL' | 'STORED' with a
generationExpression to emit ... AS (expr) VIRTUAL|STORED (MariaDB 5.2+).
invisible: true — MariaDB 10.3+ invisible columns.
const dialect = prorm.getDialectInstance();

await dialect.createTable(
  'orders',
  {
    id: { type: DataTypes.INTEGER, primaryKey: true, autoIncrement: true },
    price: { type: DataTypes.DECIMAL, precision: 10, scale: 2, allowNull: false },
    qty: { type: DataTypes.INTEGER, allowNull: false },
    // STORED generated column: total = price * qty
    total: {
      type: DataTypes.DECIMAL,
      generated: 'STORED',
      generationExpression: '`price` * `qty`',
    },
  },
  {
    engine: 'InnoDB',
    tableComment: 'Customer orders',
    // MariaDB 10.3+ system-versioned table
    systemVersioning: true,
  } as any,
);

CRUD examples#

Standard model operations work the same as any other dialect:
const User = prorm.define('User', {
  id: { type: DataTypes.INTEGER, primaryKey: true, autoIncrement: true },
  name: DataTypes.STRING(100),
  email: { type: DataTypes.STRING(255), unique: true },
  status: {
    type: DataTypes.ENUM('active', 'inactive'),
    defaultValue: 'active',
  },
});

await prorm.sync();

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

// Read
const active = await User.findAll({ where: { status: 'active' } });
const one = await User.findOne({ where: { email: 'ada@example.com' } });

// Update
await User.update({ status: 'inactive' }, { where: { id: ada.id } });

// Upsert (ON DUPLICATE KEY UPDATE under the hood)
await User.upsert(
  { id: ada.id, name: 'Ada Lovelace' },
  { updateOnDuplicate: ['name'] },
);

// Bulk insert with upsert semantics
await User.bulkCreate(
  [
    { name: 'Grace', email: 'grace@example.com' },
    { name: 'Katherine', email: 'katherine@example.com' },
  ],
  { updateOnDuplicate: ['name'] },
);

// Delete
await User.destroy({ where: { status: 'inactive' } });

Transactions#

await prorm.transaction(async (t) => {
  const user = await User.create(
    { name: 'Edsger', email: 'edsger@example.com' },
    { transaction: t },
  );
  await User.update(
    { status: 'active' },
    { where: { id: user.id }, transaction: t },
  );
  // commits automatically; throws roll back
});

Raw queries#

prorm.query runs raw SQL through the same pool. Statements starting with
SELECT, SHOW, DESCRIBE, EXPLAIN, or WITH are treated as row-returning:
const result = await prorm.query('SELECT VERSION() AS version');
console.log(result.rows[0].version); // e.g. "10.11.4-MariaDB"

// RETURNING works on writes against MariaDB 10.5+
const inserted = await prorm.query(
  "INSERT INTO `users` (`name`, `email`) VALUES ('Alan', 'alan@example.com') RETURNING `id`, `name`",
);
console.log(inserted.rows);
The query method also supports retry options for transient failures
(Deadlock, Lock wait timeout, Too many connections, connection refusals,
etc.) via query(sql, { retry: { max: 3, timeout: 1000 } }).

Introspection helpers#

getDatabaseVersion() → SELECT VERSION().
getMariaDBVersionInfo() → parsed { version, versionNumber, storageEngine },
where versionNumber encodes major*10000 + minor*100 + patch (e.g. 10.11.4
→ 110004) so you can gate feature use on the server version yourself.
showTables(), showViews(), describeTable(), showIndexes(),
showConstraints(), getCreateTable(), getTableStatus().
resetAutoIncrement(table, value?) → ALTER TABLE ... AUTO_INCREMENT[= value].
const info = await prorm.getDialectInstance().getMariaDBVersionInfo();
if (info.versionNumber >= 100500) {
  // safe to rely on INSERT ... RETURNING
}

Limitations & honest caveats#

RETURNING is INSERT/DELETE only. INSERT ... RETURNING needs MariaDB
10.5+, DELETE ... RETURNING needs 10.0.5+, and MariaDB has no
UPDATE ... RETURNING at all. The dialect emits the clause unconditionally
whenever you pass returning, so unsupported combinations fail at the server,
not in the ORM.
No DETACH PARTITION. detachPartition throws by design; use
dropPartition.
dropTrigger does not support CASCADE — passing cascade: true throws,
because MariaDB's DROP TRIGGER has no such option.
OFFSET requires a LIMIT; the dialect injects a max-BIGINT limit for
offset-only queries.
JSON is function-based, not a separate binary storage type. Everything goes
through JSON_* functions; there is no JSONB-style operator set as in
PostgreSQL — JSONB maps to JSON.
CONNECT / external engines depend on the target server actually having the
CONNECT plugin installed; the dialect only generates the DDL.

See also#

MySQL dialect — MariaDB shares most of its behavior.
mariadb — the
authoritative implementation.

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.
Capabilitymariadb
Transactions atomicyes
Savepointsyes
Isolationup to SERIALIZABLE
Transaction modesread-only no; deferrable no; constraint deferral no
RETURNINGRETURNING on INSERT
UpsertINSERT … ON DUPLICATE KEY UPDATE
JSON columnJSON (JSONB → JSON)
Vector columnVECTOR(3)
Array columnVARCHAR(255)
WHERE builder37 operator keys plus the $json: prefix; $and/$or/$not; $exists: yes; $in subquery: yes; expression operands: yes
SQL objectsfamily mariadb: triggers yes; procedures yes; functions multiStatement; materialized views emulated (procedure); sequences yes; enums inline; RLS no
StreamingqueryStream() present; LISTEN absent; createExtension() present

Related reading#

Running mariadb 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
Azure Data Explorer (Kusto) Dialect — T-SQL
Next
Materialize Dialect
Built with