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

PostgreSQL Dialect

Overview#

PostgreSQL is the ORM's most fully-featured
dialect. Unlike the compatibility-layer dialects (TiDB, CockroachDB, etc.), the
PostgresDialect is a first-class, hand-written implementation on top of the
official node-postgres (pg) driver — it does
not extend any other dialect.
PropertyValue
Dialect namepostgres
Extendsnothing — implements Dialect directly
Driverpg
Cloud SDKnone
Default port5432
Local runtimeprorm db up --dialect postgres (postgres:16.4-alpine); docker-compose.test.yml
Key facts (from src/dialects/postgres/index.ts):
Dialect name is 'postgres'; the driver library is 'pg'.
Connections are pooled (pg.Pool), with a separate dedicated pg.Client
opened lazily only for LISTEN/NOTIFY (notifications are delivered to the
specific backend that issued LISTEN, so a pooled connection can't be used).
Identifiers are double-quoted: escapeId('my_col') → "my_col", and
embedded double-quotes are doubled (" → "").
Parameters use PostgreSQL's native numbered $1, $2, … placeholders, not
?. The build* methods generate these and return a matching values array.
RETURNING is supported on INSERT / UPDATE / DELETE / UPSERT / MERGE — a
genuine PostgreSQL capability, not emulated.

Quick start#

Install#

$ npm install ts-prorm-orm pg
$ pnpm add ts-prorm-orm pg
$ yarn add ts-prorm-orm pg
$ bun add ts-prorm-orm pg
pg-copy-streams is optional: only the features that need it load it.

Connect#

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

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

export const db = new Prorm({
  dialect: 'postgres',
  url: 'postgres://app:secret@localhost:5432/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.JSONB() },
});

await db.sync(); // CREATE TABLE — see Generated SQL below
meta is JSONB, which the containment query below needs.

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 → SERIAL, BOOLEAN → BOOLEAN, DATE → TIMESTAMP, UUID → UUID, 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: 'postgres',
  host: '127.0.0.1',
  port: 5432, // default 5432 when omitted
  username: 'postgres',
  password: 'secret',
  database: 'app',
});
Notes:
The top-level Prorm option is username; internally it is mapped to the pg
driver's user field.
Constructor defaults are applied when omitted: host: 'localhost',
port: 5432, max: 20 (pool size), idleTimeoutMillis: 30000,
connectionTimeoutMillis: 2000.

Driver extras via dialectOptions#

Postgres-specific fields that aren't part of the base connection shape are
passed through the top-level dialectOptions object, which Prorm spreads onto
the dialect config (src/prorm.ts). These are forwarded to pg.Pool:
const db = new Prorm({
  dialect: 'postgres',
  host: 'db.example.com',
  username: 'app',
  password: 'secret',
  database: 'app',
  dialectOptions: {
    ssl: { rejectUnauthorized: false }, // pg `ssl` — object or boolean
    max: 40, // pool size
    idleTimeoutMillis: 10000,
    connectionTimeoutMillis: 5000,
    statementTimeout: 30000, // pg `statement_timeout`
    queryTimeout: 30000, // pg `query_timeout`
  },
});
The ssl value is passed verbatim to pg (ssl: this.config.ssl), so it
accepts anything node-postgres accepts — true, false, or a TLS options
object with ca/cert/key/rejectUnauthorized.

Schemas / search_path#

There is no schema or searchPath connection option on the Postgres
dialect — the config interface (PostgresDialectOptions) does not declare one,
so the connection uses the server's default search_path (normally public).
Schema qualification is done per operation instead:
quoteTable(table, schema) prefixes a non-public schema:
quoteTable('users', 'billing') → "billing"."users". A schema of
'public' (or omitted) is left unqualified.
View, materialized-view, trigger, and stored-procedure builders accept an
options.schema and qualify the object name the same way.
createSchema(name) / dropSchema(name, { ifExists, cascade }) and
listSchemas() manage schemas directly.
To pin a search_path for a session, run it as a raw statement:
await db.dialect.query('SET search_path TO billing, public');

Data types#

getDataTypeSql maps the ORM's cross-dialect type descriptors to PostgreSQL
types. A raw string is passed through unchanged (with one normalization: the
cross-dialect pseudo-type DATETIME, emitted by the model-sync layer for
createdAt/updatedAt/deletedAt, is rewritten to TIMESTAMP, preserving any
precision — DATETIME(6) → TIMESTAMP(6)).
ORM type descriptorGenerated SQL
{ key: 'STRING' }VARCHAR(255)
{ key: 'STRING', length: 100 }VARCHAR(100)
{ key: 'CHAR' }CHAR(1)
{ key: 'TEXT' }TEXT
{ key: 'INTEGER' }INTEGER
{ key: 'INTEGER', autoIncrement }SERIAL
{ key: 'BIGINT' }BIGINT
{ key: 'BIGINT', autoIncrement }BIGSERIAL
{ key: 'FLOAT' }REAL
{ key: 'DOUBLE' }DOUBLE PRECISION
{ key: 'DECIMAL', precision, scale }DECIMAL(precision,scale)
{ key: 'BOOLEAN' }BOOLEAN
{ key: 'DATE' }TIMESTAMP
{ key: 'DATEONLY' }DATE
{ key: 'TIME' }TIME
{ key: 'BLOB' }BYTEA
{ key: 'JSON' }JSON
{ key: 'JSONB' }JSONB
{ key: 'UUID' }UUID
{ key: 'ENUM', values: ['a','b'] }ENUM('a','b')
{ key: 'ARRAY', type: INTEGER }INTEGER[]
{ key: 'INET' } / CIDR / MACADDRINET / CIDR / MACADDR
{ key: 'HSTORE' }HSTORE
{ key: 'VECTOR', dimensions: 3 }VECTOR(3)
Notes on honest limitations:
SERIAL/BIGSERIAL are emitted only for auto-increment INTEGER/BIGINT
columns; the identity-column form (GENERATED … AS IDENTITY) is not generated
by the type mapper.
ENUM is emitted inline as ENUM('a','b'), which is not native
PostgreSQL syntax — PostgreSQL enums are named types created with
CREATE TYPE. Use the dialect's createEnumType() helper and reference the
type by name for real enum columns.
VECTOR requires the pgvector extension
(CREATE EXTENSION IF NOT EXISTS vector — see createExtension()).
GEOMETRY/GEOGRAPHY require PostGIS.
An unknown descriptor falls back to VARCHAR(255).

Placeholders: $n numbering#

Every DML builder walks the input left-to-right and emits $1, $2, … in order,
pushing the corresponding JS value onto a values array that lines up with the
placeholders. A Literal (raw SQL) value is inlined verbatim and does not
consume a placeholder number
— so numbering stays contiguous across a mix of
bound values and literals.
const { sql, values } = db.dialect.buildInsertQuery('users', {
  name: 'Ada',
  age: 36,
});
// sql:    INSERT INTO "users" ("name", "age") VALUES ($1, $2)
// values: ['Ada', 36]
For UPDATE, the SET placeholders are numbered first, then the WHERE values
are appended to the same values array (in order) so the caller passes one flat
array to the driver.

RETURNING#

INSERT, UPDATE, DELETE, UPSERT, and MERGE all accept a returning option:
returning: true → appends RETURNING *.
returning: ['id', 'created_at'] → appends
RETURNING "id", "created_at" (each column identifier-quoted).
const { sql, values } = db.dialect.buildInsertQuery(
  'users',
  { name: 'Grace', email: 'grace@example.com' },
  { returning: ['id', 'created_at'] },
);
// INSERT INTO "users" ("name", "email") VALUES ($1, $2) RETURNING "id", "created_at"
db.dialect.buildDeleteQuery('sessions', { userId: 7 }, { returning: true });
// DELETE FROM "sessions" WHERE "userId" = $1 RETURNING *
The query() method surfaces RETURNING rows: for a non-SELECT statement that
returns rows, the result's rows array is populated and rowCount is set to
the number of returned rows.

ON CONFLICT upsert#

PostgreSQL upserts use INSERT … ON CONFLICT (cols) DO UPDATE SET … with the
special excluded pseudo-row referencing the values that would have been
inserted. Two builders produce this:
buildInsertQuery(table, values, { upsert: true, conflictFields, … })
buildUpsertQuery(table, values, { conflictFields, updateOnDuplicate?, … })
conflictFields is required. PostgreSQL's ON CONFLICT must name the
columns of an existing unique or exclusion constraint — it cannot be inferred
from the inserted columns — so both builders throw if conflictFields is
missing or empty.
const { sql, values } = db.dialect.buildUpsertQuery(
  'kv',
  { k: 'theme', v: 'dark' },
  { conflictFields: ['k'] },
);
// INSERT INTO "kv" ("k", "v") VALUES ($1, $2)
//   ON CONFLICT ("k") DO UPDATE SET "k" = excluded."k", "v" = excluded."v"
updateOnDuplicate (on buildUpsertQuery) restricts which columns the
DO UPDATE SET touches; otherwise every inserted column is updated:
db.dialect.buildUpsertQuery(
  'users',
  { id: 1, name: 'Ada', seen_at: new Date() },
  { conflictFields: ['id'], updateOnDuplicate: ['seen_at'], returning: ['id'] },
);
// INSERT INTO "users" ("id", "name", "seen_at") VALUES ($1, $2, $3)
//   ON CONFLICT ("id") DO UPDATE SET "seen_at" = excluded."seen_at" RETURNING "id"
For multi-branch merge logic (update on one condition, delete on another, insert
otherwise), buildMergeQuery emits a PostgreSQL 15+ MERGE … WHEN [NOT] MATCHED statement instead. Its RETURNING support requires PostgreSQL 17+.

Arrays#

escapeArray produces a PostgreSQL ARRAY[...] literal (strings are
double-quoted, non-scalar elements are JSON-encoded and quoted). PostgreSQL
infers the element type from the target column, so untyped literals work for
both text[] and numeric arrays:
db.dialect.escape(['red', 'green', 'blue']);
// ARRAY["red", "green", "blue"]
Array operator helpers build predicate fragments:
HelperEmitted SQL
buildArrayContains('tags', ['a','b'])"tags" @> ARRAY["a", "b"]
buildArrayContainedBy('tags', ['a'])"tags" <@ ARRAY["a"]
buildArrayOverlaps('tags', ['a','b'])"tags" && ARRAY["a", "b"]
buildArrayAny('tags', 'a')'a' = ANY("tags")
buildArrayAll('scores', 10, '>')10 > ALL("scores")
// rows whose "tags" array contains both 'sql' and 'db'
const frag = db.dialect.buildArrayContains('tags', ['sql', 'db']);
const rows = await db.dialect.query(`SELECT * FROM "posts" WHERE ${frag}`);

JSON / JSONB#

Both JSON and JSONB column types are mapped directly. buildJsonPathQuery
constructs path predicates and containment/existence checks:
// data #> '{profile,age}' > $2
db.dialect.buildJsonPathQuery('data', '{profile,age}', 30, '>');
// { sql: '"data" #> $1 > $2', values: ['{profile,age}', 30] }
Operator handling (real PostgreSQL semantics, verified in the dialect source):
Containment @> / <@ — emitted as raw operators with a ::jsonb cast on
the argument: "data" @> $1::jsonb. (PostgreSQL has no function form for
containment, only the operators.)
Key existence ? — emitted via the jsonb_exists(col, $1::text)
function.
Any-key existence ?| — emitted via jsonb_exists_any(col, $1::text[]),
which correctly takes a text[] of candidate keys (distinct from the
single-key ?).
Comparison operators (=, !=, >, <, >=, <=, ~, ~*) with a path
use the #> path-extraction operator; without a path they compare the column
directly.
// documents whose JSONB "meta" contains {"active": true}
const q = db.dialect.buildJsonPathQuery('meta', '', { active: true }, '@>');
// q.sql:    "meta" @> $1::jsonb
// q.values: [{ active: true }]
const rows = await db.dialect.query(
  `SELECT * FROM "docs" WHERE ${q.sql}`,
  { replacements: q.values },
);

Beyond CRUD#

The dialect also implements genuine PostgreSQL features backing higher ORM
layers, each grounded in the driver: full-text search
(buildFullTextSearchQuery, wrapping to_tsvector/plainto_tsquery with an
optional ts_rank/ts_rank_cd ranking), LISTEN/NOTIFY over a dedicated
non-pooled client (listen/notify/unlisten, with notify using
SELECT pg_notify($1, $2)), session-level advisory locks
(pgAdvisoryLock/pgTryAdvisoryLock, each holding a dedicated pooled
connection until release()), server-side cursor streaming (queryStream),
and range/list/hash partitioning helpers.

Caveats / honest limitations#

build* methods generate SQL; they do not execute. They return
{ sql, values }; you (or the ORM's higher layers) pass them to query().
conflictFields is mandatory for upserts — both upsert builders throw
without it (see the ON CONFLICT section).
Inline ENUM('a','b') is not native PostgreSQL syntax. Prefer named enum
types via createEnumType().
SET LIMIT on UPDATE/DELETE is emitted when options.limit is given, but
standard PostgreSQL does not support LIMIT on UPDATE/DELETE; it will
error on a real server unless an extension permits it. Use a subquery on the
primary key instead.
No global schema/searchPath config. Qualify per operation, or SET search_path via a raw statement.
escape() inlines values; the parameterized build* path ($n +
values) is preferred for anything derived from user input.

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.
Capabilitypostgres
Transactions atomicyes
Savepointsyes
Isolationup to SERIALIZABLE
Transaction modesread-only yes; deferrable yes; constraint deferral yes
RETURNINGRETURNING on INSERT
UpsertINSERT … ON CONFLICT (…) DO UPDATE
JSON columnJSON (JSONB → JSONB)
Vector columnVECTOR(3)
Array columnINTEGER[]
WHERE builder62 operator keys; $and/$or/$not; $exists: yes; $in subquery: yes; expression operands: yes
SQL objectsfamily postgres: triggers yes; procedures yes; functions multiStatement; materialized views native; sequences yes; enums named; RLS policy
StreamingqueryStream() present; LISTEN present; createExtension() present

Related reading#

Running postgres 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
PolarDB Dialect
Next
Presto Dialect
Built with