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

IBM Db2 Dialect

Overview#

IBM Db2 (specifically Db2 for LUW —
Linux/Unix/Windows) is IBM's flagship relational database. This ORM's
DB2Dialect targets Db2 LUW and connects through the ibm_db driver, an
ODBC-based CLI driver that IBM ships for Node.js.
PropertyValue
Dialect namedb2
Extendsnothing — implements Dialect directly
Driveribm_db
Cloud SDKnone
Default port50000
Local runtimeprorm db up --dialect db2 (icr.io/db2_community/db2:11.5.9.0)
Db2 is a standards-leaning SQL engine, and the dialect reflects that: it uses
double-quoted delimited identifiers (like Oracle/ANSI SQL), the SQL-standard
OFFSET ... FETCH FIRST pagination clause, GENERATED ALWAYS AS IDENTITY for
auto-increment, MERGE INTO for upserts, and CREATE SEQUENCE /
NEXT VALUE FOR for sequences.
Key facts (from src/dialects/db2/index.ts):
Dialect name is 'db2'; library is 'ibm_db' (the actual driver in use).
Default port is 50000 (Db2's standard TCP/IP listener). Other structured
defaults are host: 'localhost', database: 'testdb',
username: 'db2inst1', password: ''.
Bind markers are ODBC-style positional ? placeholders, matching ibm_db
(not $1/:name).
Identifiers are double-quoted. Db2 folds unquoted identifiers to
uppercase, so anything emitted through escapeId/quoteIdentifier stays
case-sensitive and must be referenced the same way everywhere.

Quick start#

Install#

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

Connect#

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

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

export const db = new Prorm({
  dialect: 'db2',
  url: 'db2://db2inst1:secret@localhost:50000/SAMPLE',
});
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' });
MERGE statement
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,
});

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

Connection#

The dialect either assembles a Db2 keyword=value connection string from
structured options, or uses a raw connectionString you supply verbatim.
import { Prorm } from 'ts-prorm-orm';

const db = new Prorm({
  dialect: 'db2',
  host: 'db2host',
  port: 50000, // Db2 default; omit to use the injected default of 50000
  username: 'db2inst1',
  password: 'secret',
  database: 'SAMPLE',
});
Internally this becomes:
DATABASE=SAMPLE;HOSTNAME=db2host;PORT=50000;PROTOCOL=TCPIP;UID=db2inst1;PWD=secret;
Db2-specific options (DB2DialectOptions):
connectionString — a raw override, e.g.
"DATABASE=x;HOSTNAME=y;PORT=50000;PROTOCOL=TCPIP;UID=u;PWD=p;". When set, the
structured host/port/etc. fields are ignored.
schema — default schema for operations (qualifies quoteTable).
ssl: true — appends SECURITY=SSL to the connection string.
extraConnectionParams — a Record<string, string> of extra
keyword=value pairs appended to the string.
pool — pool options (max defaults to 10); retry — connection retry
options (retries on Db2 network errors like SQL30081N, SQL30061N,
SQL1224N).
const db = new Prorm({
  dialect: 'db2',
  dialectOptions: {
    connectionString:
      'DATABASE=SAMPLE;HOSTNAME=db2host;PORT=50000;PROTOCOL=TCPIP;UID=u;PWD=p;',
  },
});
On connect() the dialect opens an ibm_db pool, verifies connectivity by
opening and immediately closing one connection, and marks itself connected.

Data types#

Type mapping is handled by getDataTypeSql (via mapDataType). Verified in
tests/dialects/db2.test.ts:
ORM type descriptorGenerated SQL
'STRING' / { key: 'STRING' }VARCHAR(255)
{ key: 'STRING', length: 100 }VARCHAR(100)
{ key: 'STRING', length: 'max' }CLOB
{ key: 'CHAR', length: 10 }CHAR(10)
'TEXT'CLOB
'INTEGER'INTEGER
{ key: 'INTEGER', length: 1 } / length: 2SMALLINT
{ key: 'INTEGER', length: 8 }BIGINT
'BIGINT'BIGINT
'FLOAT'REAL
'DOUBLE'DOUBLE
{ key: 'DECIMAL', precision: 12, scale: 4 }DECIMAL(12,4)
'BOOLEAN'BOOLEAN
'DATE' / 'DATETIME' / 'TIMESTAMP'TIMESTAMP
{ key: 'TIMESTAMP', precision: 12 }TIMESTAMP(12)
'DATEONLY'DATE
'TIME'TIME
'BLOB'BLOB
'JSON'CLOB
'JSONB'BLOB
'UUID'CHAR(36)
{ key: 'ENUM', values: [...] }VARCHAR(255)
'GEOMETRY'DB2GSE.ST_GEOMETRY
Note that Db2 has no native JSON/JSONB column type, so JSON is stored as
CLOB (text) and JSONB as BLOB (binary). ENUM degrades to a plain
VARCHAR(255) — Db2 has no enum type. Unknown keys fall back to VARCHAR(255).

Pagination — OFFSET ... FETCH FIRST n ROWS ONLY#

Db2 LUW (9.7+) uses the SQL-standard row-limiting clause rather than MySQL's
LIMIT/OFFSET. buildLimitOffset emits OFFSET first, then FETCH FIRST
(the order Db2 requires when both are present):
db.dialect.buildLimitOffset(10, 20);
This is applied automatically by buildSelectQuery when limit/offset are
set:
db.dialect.buildSelectQuery({
  tableName: 'Users',
  where: { active: true },
  order: [['created_at', 'DESC']],
  limit: 10,
  offset: 20,
});
With lock set, buildSelectQuery appends FOR UPDATE (and WITH RS for a
shared/'SHARE' lock).

Identity columns#

Db2 auto-increment uses GENERATED ALWAYS AS IDENTITY. A column with
autoIncrement: true emits:
await db.dialect.createTable('Users', {
  id: { type: 'INTEGER', autoIncrement: true, allowNull: false, primaryKey: true },
  name: { type: 'STRING' },
});
Because the column is GENERATED ALWAYS, the application cannot supply its own
value for it — Db2 always generates it. A defaultValue is ignored when
autoIncrement is set.

Sequences#

For standalone sequence-based keys, Db2 offers first-class sequences:
await db.dialect.createSequence({
  name: 'order_seq',
  startWith: 1000,
  incrementBy: 1,
  cache: 20,
});

const next = await db.dialect.nextSequenceValue('order_seq');
nextSequenceValue runs SELECT NEXT VALUE FOR "order_seq" ... FROM SYSIBM.SYSDUMMY1; currSequenceValue uses PREVIOUS VALUE FOR.

RETURNING via FINAL TABLE / OLD TABLE#

Db2 has no RETURNING clause, but it supports the standard data-change-table
wrappers, and the dialect uses them when you pass returning. buildInsertQuery
and buildUpdateQuery wrap the statement in SELECT ... FROM FINAL TABLE (...);
buildDeleteQuery uses OLD TABLE:
db.dialect.buildInsertQuery(
  'Users',
  { name: 'Ada', email: 'a@x.io' },
  { returning: ['id', 'name'] },
);
db.dialect.buildDeleteQuery('Users', { id: 1 }, { returning: true });
buildDeleteQuery with { truncate: true } instead emits
TRUNCATE TABLE "Users" IMMEDIATE.

Upsert — MERGE INTO#

Db2 has no INSERT ... ON DUPLICATE KEY/ON CONFLICT. buildUpsertQuery emits
a MERGE against a single-row VALUES source:
db.dialect.buildUpsertQuery(
  'kv',
  { k: 'a', v: 1 },
  { conflictFields: ['k'], updateOnDuplicate: ['v'] },
);
If conflictFields is omitted, the first column is used as the match key; if
updateOnDuplicate is omitted, every non-key column is updated.
Db2 does not support RETURNING on MERGE. Passing returning throws:
Db2 does not support a RETURNING clause on MERGE. Re-fetch the row after the upsert instead.

Other Db2-specific behavior#

Row compression. Db2TableOptions.compress controls
COMPRESS YES ADAPTIVE ('ADAPTIVE'), COMPRESS YES STATIC ('STATIC'), or
COMPRESS NO (false). It is emitted on CREATE TABLE and can be changed
later via alterTableCompression, which follows the ALTER with a
best-effort REORG TABLE (failures swallowed, since REORG needs elevated
privileges).
Materialized views are MQTs. createMaterializedView emits a
CREATE TABLE ... AS (query) DATA INITIALLY DEFERRED REFRESH {DEFERRED|IMMEDIATE}
Materialized Query Table, then populates it with REFRESH TABLE unless
withData: false. MQTs are identified by TYPE = 'S' in SYSCAT.TABLES.
Temporal tables. The dialect has first-class support for Db2's bitemporal
features — system-period (createSystemTemporalTable, using
GENERATED ALWAYS AS ROW BEGIN/END + PERIOD SYSTEM_TIME + ADD VERSIONING)
and application-period (createApplicationTemporalTable, PERIOD BUSINESS_TIME) — plus FOR SYSTEM_TIME / FOR BUSINESS_TIME query clauses.
Partitioning is RANGE-only. createPartitionedTable emits
PARTITION BY RANGE (...); requesting list or hash throws
(Db2 only supports RANGE partitioning ...).
Recursive CTEs. buildRecursiveCteClause emits standard
WITH name(cols) AS (base UNION ALL recursive). Db2 requires UNION ALL for
recursion.
DROP SCHEMA is RESTRICT-only. Db2 has no CASCADE; the schema must be
empty. The dialect always appends RESTRICT.

Not supported#

These throw explicit errors rather than emitting invalid SQL:
Extensions — createExtension/dropExtension/getExtensions/
hasExtension all throw (Extensions are not supported by Db2. This is a PostgreSQL-specific feature...).
Fulltext indexes — throw (... requires Net Search Extender).
Spatial indexes — throw (... requires Db2 Spatial Extender).

Transactions#

Db2 transactions via ibm_db are pinned to a single connection: the
connection that issued beginTransaction() must be the one that commits or
rolls back. startTransaction() returns a DB2Transaction carrying its own
connection, and query() routes any statement whose options.transaction is
that object onto the pinned connection (rather than a fresh pooled, autocommit
connection). Passing a query to a transaction that has already finished throws.

Caveats / not-yet-verified#

SQL generation is verified; live execution is not. The SQL shown here is
produced and asserted by the pure/synchronous build* builders in
tests/dialects/db2.test.ts, which run without any database connection.
Runtime behavior against a live Db2 LUW server (identity generation,
MERGE, FETCH FIRST, MQT refresh, temporal versioning) has not been
exercised end-to-end here and requires a running Db2 instance plus the
ibm_db CLI driver to confirm.
ibm_db is an ODBC/CLI driver. It ships a native client library; ensure
the platform is supported and the driver installs cleanly before relying on
live connectivity.
Boolean encoding. escape() renders JS booleans as 1/0, not the Db2
BOOLEAN literals TRUE/FALSE — relevant only for values inlined via
escape() rather than bound as ? parameters.

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.
Capabilitydb2
Transactions atomicyes
Savepointsyes
Isolationup to SERIALIZABLE; native levels UR, CS, RS, RR
Transaction modesread-only no; deferrable no; constraint deferral no
RETURNINGnot emitted; returning is accepted and ignored
UpsertMERGE INTO … WHEN MATCHED / WHEN NOT MATCHED
JSON columnCLOB (JSONB → BLOB)
Vector columnVECTOR(3, FLOAT32)
Array columnVARCHAR(255)
WHERE builder32 operator keys; $and/$or/$not; $exists: yes; $in subquery: yes; expression operands: yes
SQL objectsfamily db2: triggers yes; procedures yes; functions multiStatement; materialized views native; sequences yes; enums check; RLS no
StreamingqueryStream() present; LISTEN absent; createExtension() present

Related reading#

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