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

Aurora RDS Data API Dialect (`rdsdata`)

Overview#

The RDS Data API
runs SQL against an Aurora PostgreSQL or Aurora MySQL cluster over
HTTPS, through the AWS SDK: no socket, no pool, no VPC route to the database,
and no database password in the application. Every call names the cluster
(resourceArn) and a Secrets Manager secret holding the database credentials
(secretArn), and is signed with the caller's IAM credentials.
PropertyValue
Dialect namerdsdata
ClassRdsDataDialect
SQL grammarPostgresDialect (engine: 'postgres', default) or MySQLDialect (engine: 'mysql')
Driver@aws-sdk/client-rds-data (optional peer, loaded on connect())
Portnone of its own — HTTPS, 443 (RDS_DATA_DEFAULT_PORT)
Extendsnothing — implements Dialect directly
Cloud SDK@aws-sdk/client-rds-data
Default portnone — HTTPS
Local runtimenone — hosted service only

Quick start#

Install#

$ npm install ts-prorm-orm @aws-sdk/client-rds-data
$ pnpm add ts-prorm-orm @aws-sdk/client-rds-data
$ yarn add ts-prorm-orm @aws-sdk/client-rds-data
$ bun add ts-prorm-orm @aws-sdk/client-rds-data

Connect#

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

export const db = new Prorm({
  dialect: 'rdsdata',
  database: 'app',
  dialectOptions: {
    engine: 'postgres', // or 'mysql'
    resourceArn: 'arn:aws:rds:us-east-1:123456789012:cluster:app-cluster',
    secretArn: 'arn:aws:secretsmanager:us-east-1:123456789012:secret:app-AbCdEf',
    region: 'us-east-1',
  },
});

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#

await db.transaction(async (t) => {
  await User.create({ email: 'grace@example.com', name: 'Grace' }, { transaction: t });
  await User.update({ name: 'Grace Hopper' }, { where: { email: 'grace@example.com' }, transaction: t });
});
[!WARNING] No savepoints
capabilitiesOf() reports no savepoints for this dialect, so a transaction() nested inside another one throws.

Table sampling#

sample on the select builder reads a random fraction of the table, for estimates over large tables:
const sample = db.getDialectInstance()!.buildSelectQuery({
  tableName: 'users',
  sample: { method: 'BERNOULLI', percent: 10 },
});
await db.query(sample.sql);
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: 'rdsdata',
  database: 'app',
  dialectOptions: {
    engine: 'postgres', // or 'mysql'
    resourceArn: 'arn:aws:rds:us-east-1:123456789012:cluster:app-cluster',
    secretArn: 'arn:aws:secretsmanager:us-east-1:123456789012:secret:app-AbCdEf',
    region: 'us-east-1',
    // credentials, endpoint (VPC/FIPS endpoint), resultSetOptions, continueAfterTimeout
  },
});
OptionMeaning
engine'postgres' (default) or 'mysql' — picks the SQL grammar
resourceArnThe Aurora cluster ARN (…:cluster:<id>); 11–100 characters
secretArnSecret with the database user and password; 11–100 characters
databaseDatabase for every call (≤ 64 characters)
region, endpoint, credentialsPassed to RDSDataClient; default: the SDK's chains
clientA ready client with the five methods (e.g. new RDSData({...})); the SDK is then not loaded here
continueAfterTimeout'ddl' (default), true or false — see Timeouts
resultSetOptionsPassed through, e.g. { longReturnType: 'STRING' } for exact 64-bit values
resumeRetries, resumeRetryDelayMsRetries after DatabaseResumingException (default 3 × 5 s)
connect() validates the options and builds the client; it makes no call (a
probe statement would wake a paused Serverless v2 instance every time).
Construction loads nothing.
Refused at connect():
schema — Aurora clusters reject Data API calls that include the schema
parameter. Qualify names (quoteTable(table, schema)); on MySQL set
database.
password — credentials come from the secret; a password would be silently
ignored.
A non-cluster resourceArn — the Data API serves Aurora clusters only.
The cluster needs the Data API enabled, and a version that supports it
(Aurora PostgreSQL 13.11+, 14.8+, 15.3+, 16.1+, 17.4+; Aurora MySQL 3.07+;
provisioned or Serverless v2; not T instance classes). On Aurora PostgreSQL 14+
the database user's password must use scram-sha-256.

One class, two grammars#

RdsDataDialect holds an unconnected PostgresDialect or MySQLDialect
(dialect.grammar) rather than extending one: a class cannot choose its
superclass per instance, and the transport is identical for both engines.
Every grammar method the facade does not define is forwarded to it, and the
grammar's own I/O entry points (query, transactions, queryStream, the
version probe, the PostgreSQL session features) are pointed back at the
facade, so inherited helpers such as createTable() or bulkInsert() go out
over the Data API.

Parameters#

The Data API binds named parameters (:name) with typed values. The
grammars' positional placeholders — $1 (PostgreSQL) and ? (MySQL) — are
rewritten to :p1, :p2, …, skipping string literals, quoted identifiers,
comments and PostgreSQL dollar-quoted bodies.
JavaScript valueSent as
null / undefinedisNull
booleanbooleanValue
safe integer / bigintlongValue
bigint beyond ±2^53stringValue, typeHint DECIMAL
other numberdoubleValue (NaN/Infinity refused)
stringstringValue
DatestringValue YYYY-MM-DD HH:MM:SS.FFF (UTC), typeHint TIMESTAMP
Buffer / Uint8ArrayblobValue
plain objectJSON stringValue, typeHint JSON
RdsDataTypes.decimal/uuid/json/date/time/timestamp(v)stringValue with that typeHint (formats checked)
array, raw Literalinlined by the grammar's escape() — the Data API has no array parameters
A plain object as replacements is sent as named parameters for the :names
the SQL uses; a :name without a value is refused.
await db.query('SELECT * FROM orders WHERE id = :id AND total > :min', {
  replacements: { id: RdsDataTypes.uuid(orderId), min: RdsDataTypes.decimal('10.00') },
});

Results#

Rows come from records + columnMetadata (includeResultMetadata: true),
not from formatRecordsAs: 'JSON': typed fields keep BLOBs as Buffers and
64-bit integers out of JSON.parse. Dates and times come back as strings
(the Data API returns them as stringValue; Aurora PostgreSQL returns
TIMESTAMPTZ in UTC). On MySQL, generatedFields becomes lastInsertRowid;
on PostgreSQL (which does not support generatedFields) an INSERT gets
RETURNING *, as the postgres dialect does.

Limits#

Limit (AWS-documented)What the dialect does
Response ≤ 1 MiB; ≤ 64 KB per rowError annotated; queryStream() pages with LIMIT/OFFSET
SQL text ≤ 65,536 charactersRefused before sending
HTTP request ≤ 4 MiB (headers + JSON)Refused before sending; an oversize batch() in a transaction is split
Call cancelled after 45 scontinueAfterTimeout (see below)
One statement per callSeveral statements refused before sending
Transaction: 3 min idle, 24 h totalChecked before each call; server error annotated
One request at a time per transactionCalls on a transaction are queued
No array parametersArrays inlined as literals
schema parameter rejectedRefused at connect()
All values are exported as RDS_DATA_LIMITS.

Timeouts#

A Data API call is cancelled after 45 seconds. With continueAfterTimeout
the call still returns a timeout error, but the statement keeps running. AWS
recommends it for DDL, because a DDL statement cut off mid-way can leave
errors or damaged structures — so the default 'ddl' sends it for
CREATE/ALTER/DROP/RENAME/TRUNCATE/COMMENT/GRANT/REVOKE outside a
transaction. Override per call: query(sql, { continueAfterTimeout: true }).
Keep any SDK/HTTP timeout above 45 s (AWS suggests at least a minute) so the
client does not give up — and retry — while the statement is still running.

Transactions#

const tx = await db.getDialect().startTransaction(); // BeginTransaction
await tx.query('UPDATE accounts SET balance = balance - $1 WHERE id = $2', {
  replacements: [10, 1],
});
await tx.commit(); // CommitTransaction
transactionId is sent with every call made through tx.query() or
query(sql, { transaction: tx }). Refused:
An isolation level — BeginTransaction has none. Set the cluster default
in its DB parameter group (default_transaction_isolation on PostgreSQL,
transaction_isolation on MySQL).
DDL inside an Aurora MySQL transaction — MySQL commits the transaction
implicitly before DDL. Run it on its own.

Batches#

const { sql } = dialect.buildInsertQuery('events', { kind: '', at: new Date() });
await dialect.batch(
  sql,
  rows.map((r) => [r.kind, r.at]),
  { transaction: tx },
);
batch() is BatchExecuteStatement: one DML statement over many parameter
sets, no result set (a SELECT is refused), trailing ; removed. Outside a
transaction it is one call and commits as a unit; a batch over 4 MiB is
refused. Inside a transaction an oversize batch is split into several calls,
committed together.

Refused: features that need a held connection#

Each call is a separate HTTPS request, so nothing that needs a connection kept
open between calls works:
MethodAlternative
listen / unlisten / notifyThe postgres dialect on the cluster endpoint, or SNS/SQS/EventBridge
copyFrom (COPY FROM STDIN)batch(), or aws_s3.table_import_from_s3 / LOAD DATA FROM S3
copyTo (COPY TO STDOUT)queryStream(), or aws_s3.query_export_to_s3 / SELECT … INTO OUTFILE S3
pgAdvisoryLock / pgTryAdvisoryLockpg_advisory_xact_lock inside a transaction
queryStream() uses LIMIT/OFFSET pages instead of a server-side cursor.

References#

Using the RDS Data API
Limitations
Operations reference and type mapping
Timeout behaviour
Troubleshooting
ExecuteStatement,
BatchExecuteStatement,
BeginTransaction
Region and version availability

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.
Capabilityrdsdata
Transactions atomicyes
Savepointsyes
Isolationup to SERIALIZABLE
Transaction modesread-only no; deferrable no; constraint deferral no
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 unknown: triggers no; procedures no; functions no; materialized views no; sequences no; enums check; RLS no
StreamingqueryStream() present; LISTEN present; createExtension() present

Testing#

tests/dialects/rdsdata.test.ts exercises the dialect with a mocked driver, so nothing touches a server.

See also#

All dialects — the family tree and the capability matrix
Modified at 2026-10-04 00:40:16
Previous
QuestDB Dialect
Next
Amazon RDS for Db2 Dialect
Built with