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

OceanBase Dialect

Overview#

OceanBase is a distributed relational database with
two compatibility modes — MySQL and Oracle — chosen per tenant when the
tenant is created. The MySQL mode is the mainstream one, and it is what this
dialect models.
PropertyValue
Dialect nameoceanbase
ExtendsMySQLDialect (mysql)
Drivermysql2
Cloud SDKnone
Default port2881
Local runtimeself-hosted; no image in this repo
Because MySQL mode speaks the MySQL client/server protocol, OceanBaseDialect
extends MySQLDialect and reuses MySQL's mysql2 driver verbatim —
connection pooling, identifier escaping, query execution, streaming, and most
DDL/DML builders are inherited unchanged. Only the grammar and capabilities that
genuinely differ are overridden.
Oracle mode is not covered. A tenant created in Oracle compatibility mode
speaks a different SQL grammar entirely (ROWNUM, DUAL, PL/SQL packages,
sequence-based keys). This dialect will emit MySQL-mode SQL against it and the
server will reject it. There is no oceanbase-oracle dialect today.
Key facts (from src/dialects/oceanbase/index.ts):
Dialect name is 'oceanbase'. The underlying driver library stays mysql2.
Default SQL port is 2881 — an observer's own MySQL port. MySQL's 3306
reaches nothing on an OceanBase cluster. Connections through obproxy (ODP)
use 2883
; pass port: 2883 for those.
A connection selects its tenant through the username, not a separate
field. See below.

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: 'oceanbase',
  host: 'localhost',
  database: 'test',
  username: 'app',
  password: process.env.DB_PASSWORD,
  dialectOptions: {
    tenant: 'app_tenant', // sent as app@app_tenant
  },
});
import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'oceanbase',
  url: 'oceanbase://app:secret@localhost:2881/test',
  dialectOptions: {
    tenant: 'app_tenant', // sent as app@app_tenant
  },
});
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(() => {});
});
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 db = new Prorm({
  dialect: 'oceanbase',
  host: '127.0.0.1',
  port: 2881, // observer direct; use 2883 through obproxy
  username: 'app',
  password: '',
  database: 'test',
  dialectOptions: {
    tenant: 'prod_tenant', // composed into the username as app@prod_tenant
    cluster: 'obcluster', // optional; appended as #obcluster
  },
});

Tenanted usernames#

OceanBase has no tenant field on the wire. The tenant is selected by the
username, in one of two documented forms:
user@tenant#cluster
cluster:tenant:user
Omitting the tenant lands the connection in the sys tenant, which is the
cluster's own administrative tenant and not where application schemas live —
a mistake that shows up as "table doesn't exist" rather than as a login error.
Passing tenant (and optionally cluster) composes the username for you:
OceanBaseDialect.buildTenantUsername('app', 'prod_tenant', 'obcluster');
// 'app@prod_tenant#obcluster'
A username that already carries an @ or a : is left untouched — you have
spelled the tenant out yourself, and re-appending would produce
root@sys@prod_tenant, which authenticates as nothing.
The cluster suffix is required by obproxy when it fronts more than one
cluster, and ignored when connecting straight to an observer.

What differs from MySQL#

OceanBaseDialect extends MySQLDialect (mysql) and
overrides 15 of its methods (Object.getOwnPropertyNames(OceanBaseDialect.prototype),
computed by the scratch test); everything else is inherited unchanged.
AreaOverridden
Connection and executionstartTransaction
DML buildersbuildInsertQuery, buildUpsertQuery, escapeSqlString, formatDefaultValue
TypesbuildColumnSql
DDL and schemabuildCreateTableGroupSql, buildCreateTableSql, buildTableConstraintSql, buildTableOptionsSql, createTable, createTableGroup, dropTableGroup
OtherbuildDuplicateKeyUpdateClause, legacyNeedsModern

OceanBase-specific features#

Distributed table options#

CREATE TABLE accepts a set of options controlling how the table is replicated,
placed and stored across the cluster. None of these are valid MySQL syntax.
OptionEmitted asWhat it controls
replicaNumREPLICA_NUM = nNumber of replicas held for this table
duplicateScopeDUPLICATE_SCOPE = 'cluster'Broadcast the table to every zone so joins stay local
localityLOCALITY = 'F@zone1,F@zone2'Replica type and placement
primaryZonePRIMARY_ZONE = 'zone1'Zone holding the leader replica
tablegroupTABLEGROUP = nameCo-locate this table's partitions with the group's
blockSizeBLOCK_SIZE = 16384Microblock size in bytes
compressionCOMPRESSION = 'zstd_1.0'Storage compression algorithm
useBloomFilterUSE_BLOOM_FILTER = TRUEBloom filter for point lookups
tabletSizeTABLET_SIZE = 134217728Bytes per tablet before it splits
db.dialect.buildCreateTableSql(
  'orders',
  { id: { type: 'BIGINT', primaryKey: true } },
  { replicaNum: 3, duplicateScope: 'cluster', primaryZone: 'zone1' },
);
A table that asks for none of these produces exactly the DDL the MySQL dialect
would produce, and createTable() delegates straight to the MySQL
implementation in that case, so the common path keeps the base dialect's full
post-creation handling.

Tablegroups#

A tablegroup binds tables whose matching partitions should live on the same
server, so a join between them never crosses the network.
db.dialect.buildCreateTableGroupSql('tg_orders', { sharding: 'PARTITION' });
SHARDING takes NONE, PARTITION or ADAPTIVE. PARTITION requires member
tables to share a partition scheme. createTableGroup() and dropTableGroup()
build and execute; buildCreateTableGroupSql() is pure/synchronous.

Divergences from MySQL#

Isolation levels — only two exist#

OceanBase's MySQL mode implements READ COMMITTED (the default) and
REPEATABLE READ. READ UNCOMMITTED and SERIALIZABLE are not available.
The base MySQL dialect passes whatever level it is given straight into
SET TRANSACTION ISOLATION LEVEL, which would either fail deep inside the
driver or silently run the transaction at a level the caller did not choose.
A silently downgraded isolation level is a correctness bug nobody can see, so
startTransaction() rejects the unsupported ones by name:
OceanBase (MySQL mode) does not support the SERIALIZABLE isolation level.
Supported levels are READ COMMITTED and REPEATABLE READ.

Upsert — the classic VALUES(col) form#

MySQL 8.0.19 introduced the row-alias INSERT form (INSERT ... VALUES (...) AS new_vals ON DUPLICATE KEY UPDATE col = new_vals.col), which the base
MySQLDialect emits. OceanBase's support for that form is not documented
either way
, and the classic VALUES(col) function form is accepted by both
engines, so OceanBaseDialect overrides buildInsertQuery (with
options.upsert) and buildUpsertQuery to emit the classic form:
db.dialect.buildUpsertQuery('kv', { k: 'a', v: 1 });
This is a deliberately conservative choice, not a claim that the row-alias
form is rejected. If you confirm OceanBase accepts it, the classic form still
works — it is only deprecated in upstream MySQL, not removed.
OceanBase's MySQL mode has no RETURNING clause; passing returning to
buildUpsertQuery throws.

AUTO_INCREMENT is neither gapless nor, by default, monotonic#

This changes no SQL, but it changes what the SQL means, and it is the OceanBase
behaviour most likely to break an application ported from MySQL.
In NOORDER mode (the default) each observer caches a disjoint range of the
sequence — [1,100] on one node, [101,200] on another — so generated values
are globally unique but arrive out of order and with visible jumps between
ranges. ORDER mode restores monotonicity by routing allocation through a
single node, at that node's cost. Releases before v4.0 guarantee neither
contiguity nor global ordering, only that values increase within a partition.
Any code that treats an auto-increment key as an insertion order — "the highest
id is the newest row", cursor pagination on the primary key, gap detection — is
wrong on OceanBase. The relevant tenant variables are auto_increment_offset,
auto_increment_increment and auto_increment_cache_size.

ENGINE= is parsed and ignored#

OceanBase has one LSM-tree storage engine. There is no InnoDB and no pluggable
engine. The engine table option is still emitted so DDL carried over from
MySQL round-trips, but it has no effect.

Deliberately not rejected#

Two things this dialect could have thrown on, and does not, because the answer
depends on the server version:
Spatial / GIS types. Unlike TiDB, OceanBase does support GEOMETRY,
POINT, POLYGON and the ST_* functions — added in 4.1 and expanded in
4.2.2. Spatial types are therefore passed straight through to the MySQL
type mapping. Whether SPATIAL INDEX itself can be created is not documented
either way, so it is not rejected either.
FULLTEXT and HASH indexes. Documented as unsupported in older releases and
as available from 4.2.2. A hard error keyed to the wrong version would break a
cluster that supports them perfectly well, so neither is rejected. If your
cluster predates them, the server will say so.

Inherited MySQL behavior#

Standard CRUD and most DDL are inherited from MySQLDialect and behave exactly
as documented for the MySQL dialect — identifiers are backtick-quoted, SELECT
/ INSERT / UPDATE / DELETE builders, JSON helpers, FOR UPDATE /
LOCK IN SHARE MODE, and the full type mapping (see the
MySQL dialect page). Foreign keys, CHECK constraints, generated
columns, triggers and stored procedures are all supported by OceanBase, so the
inherited builders for those are left alone. OceanBase's partitioning is a
superset of MySQL's (it adds non-template sub-partitioning and more
sub-partition methods), so inherited partition DDL is valid as-is.

Caveats / not-yet-verified#

SQL generation is verified; live execution is not. Every SQL snippet on
this page is the exact output of a builder asserted in
tests/dialects/oceanbase.test.ts, which runs without any database
connection
. None of it has been executed against a live OceanBase cluster
in this repository.
The row-alias upsert question is open. As above: the classic form is
emitted because it is known-good on both engines, not because the row-alias
form is known-bad.
Reserved words have not been diffed. OceanBase publishes a
reserved-keywords list for MySQL mode; it was not reachable while this dialect
was written, so no keyword-specific quoting differences are modelled. All
identifiers are backtick-quoted by the inherited escaping, which covers the
common case.
SPATIAL INDEX support is unconfirmed. Spatial types are confirmed from
4.1; whether an index can be built on one is not.
Introspection helpers inherited from MySQL (showTables, describeTable,
getCreateTable, showIndexes, showConstraints, and the
INFORMATION_SCHEMA-based partition helpers) assume MySQL system-catalog
shapes and have not been checked against OceanBase's catalogs.
Trigger support is version-sensitive. Triggers are supported, and 4.2.1
LTS added PRECEDES/FOLLOWS ordering, but there is at least one community
report of trigger creation failing on 4.2.1.2 specifically.

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.
Capabilityoceanbase
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 unknown: triggers no; procedures no; functions no; materialized views no; sequences no; enums check; RLS no
StreamingqueryStream() present; LISTEN absent; createExtension() present

Related reading#

All dialects — what each engine supports
MySQL dialect — everything inherited unchanged
Data types — how each type maps to this engine
Querying — how a FindOptions becomes SQL
Modified at 2026-10-04 00:40:16
Previous
Neon Dialect
Next
openGauss Dialect
Built with