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 DSQL Dialect

Overview#

Amazon Aurora DSQL is a serverless,
distributed SQL database that runs active-active across Regions without locks.
It speaks the PostgreSQL wire protocol, so AuroraDSQLDialect extends
PostgresDialect
and reuses the pg driver, pooling, $n binding,
identifier escaping and every read-path builder unchanged.
DSQL is a deliberate subset of PostgreSQL 16. The pieces it leaves out are
the ones that need locks or per-node state, and this dialect refuses each of
them by name instead of sending SQL DSQL rejects with a bare syntax error.
PropertyValue
Dialect nameauroradsql
ExtendsPostgresDialect
Driverpg (+ @aws-sdk/dsql-signer)
Default port5432
Databasealways postgres
Cloud SDK@aws-sdk/dsql-signer
Local runtimenone — hosted service only

Quick start#

Install#

$ npm install ts-prorm-orm @aws-sdk/dsql-signer
$ pnpm add ts-prorm-orm @aws-sdk/dsql-signer
$ yarn add ts-prorm-orm @aws-sdk/dsql-signer
$ bun add ts-prorm-orm @aws-sdk/dsql-signer

Connect#

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

export const db = new Prorm({
  dialect: 'auroradsql',
  host: 'abc123.dsql.us-east-1.on.aws', // region is read from the host
  username: 'admin', // no password: an IAM token is minted per connection
});

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,
});

Managed and cloud variants#

One tab per way of logging in. The token-based ones fetch a short-lived token for every new pooled connection, so a pool that outlives a token keeps working; Cloud authentication covers the providers, caching and TLS rules behind them.
import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'auroradsql',
  host: 'abc123.dsql.us-east-1.on.aws',
  username: 'admin', // admin gets getDbConnectAdminAuthToken()
});
Needs @aws-sdk/dsql-signer installed next to the driver.
import { Prorm } from 'ts-prorm-orm';

declare function fetchTokenFromVault(): Promise<string>;

export const db = new Prorm({
  dialect: 'auroradsql',
  host: 'abc123.dsql.us-east-1.on.aws',
  username: 'app_role',
  dialectOptions: {
    tokenProvider: async () => fetchTokenFromVault(), // takes precedence over the signer
  },
});

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,
});

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 → refused, BOOLEAN → BOOLEAN, DATE → TIMESTAMP, UUID → UUID, JSON → JSON. The type comparison lines the major engines up side by side.

Connection#

DSQL authenticates with a short-lived IAM token used as the password, and
requires TLS.
import { AuroraDSQLDialect } from 'prorm/dialects/auroradsql';

const dialect = new AuroraDSQLDialect({
  host: 'abc123.dsql.us-east-1.on.aws', // region is parsed from the host
  username: 'admin',                     // the default
});
await dialect.connect();
With no password, the dialect hands pg a password function that mints a
fresh token with @aws-sdk/dsql-signer for every new pooled connection
(getDbConnectAdminAuthToken() for admin, getDbConnectAuthToken() for any
other role). A token only needs to be valid at connect time, and connections
are closed by DSQL after an hour, so this is the one moment a token is needed.
Install the signer with npm install @aws-sdk/dsql-signer; it is loaded
lazily, only when a token is minted.
OptionMeaning
tokenProviderYour own () => string | Promise<string>; takes precedence
passwordA pre-minted token, or a token function
regionNeeded only when the host is not <id>.dsql.<region>.on.aws
tokenExpiresInToken lifetime in seconds (DSQL default 900)
identityCacheCACHE for autoIncrement identity columns (default 65536)
ssl defaults to { rejectUnauthorized: true }; ssl: false throws.
dialect.resolveAuthToken() returns the token the next connection would use.

What differs from Postgres#

AuroraDSQLDialect extends PostgresDialect (postgres) and
overrides 75 of its methods (Object.getOwnPropertyNames(AuroraDSQLDialect.prototype),
computed by the scratch test); everything else is inherited unchanged.
AreaOverridden
Connection and executionconnect, listen, notify, startTransaction, unlisten
DML buildersbuildDeleteQuery, buildSelectQuery, bulkInsert, formatDefaultValue
TypesbuildAddColumnSql, buildColumnSql, canonicalTypeSql, createEnumType, ensureEnumTypes, getDataTypeSql, unsupportedType
DDL and schemaaddColumn, addForeignKey, addIndex, attachPartition, buildAddForeignKeySql, buildCreateIndexAsyncSql, buildCreateSequenceSql, buildCreateTableSql, buildTableConstraintSql, changeColumn, createDatabaseSQL, createExtension, createIndex, createIndexAsync, createMaterializedView, createPartition, createPartitionedTable, createPolicy, createSavepointSQL, createSequence, createStoredProcedure, createTable, createTrigger, detachPartition, disableRLS, dropDatabaseSQL, dropExtension, dropPartition, dropPolicy, dropTrigger, enableRLS, refreshMaterializedView, truncateRefusal
IntrospectionassertLockSupported, getExtensions, getJob, getLockOptions, hasExtension, hasPolicy, hasTrigger, isRetryableError, resolveAuthToken
OtherbuildJobStatusQuery, buildReferencesSql, buildValidateConstraintSql, buildWaitForJobQuery, indexOptionsToAsync, matviewRefusal, notifyRefusal, partitionRefusal, referentialAction, releaseSavepointSQL, rlsRefusal, rollbackToSavepointSQL, runTransaction, savepointRefusal, serialRefusal, uuidPrimaryKey, waitForJob

Optimistic concurrency#

Nothing in DSQL waits for a lock. A conflicting transaction fails at COMMIT
with SQLSTATE 40001 and an OCC code in the message:
OC000 — another transaction changed the same row;
OC001 — the schema catalog changed under this session.
Both are resolved by running the whole transaction again.
AuroraDSQLDialect.isRetryableError(err); // true for 40001 / OC000 / OC001
AuroraDSQLDialect.occConflictCode(err);  // 'OC000' | 'OC001' | null

await dialect.runTransaction(async (tx) => {
  // may run more than once — keep it idempotent apart from its DB effects
}, { maxRetries: 5, baseDelayMs: 20 });
The predicate works on raw pg errors and on the wrapped Error the inherited
query() rethrows (which keeps DSQL's message but loses the code).

Transaction limits#

LimitValue
IsolationREPEATABLE READ only — anything else throws
DDLone statement per transaction, never mixed with DML
Rows modified3,000 per transaction (bulkInsert refuses more)
Data modified10 MiB per transaction
Duration5 minutes
SAVEPOINTnot supported — refused
They are exported as AURORA_DSQL_LIMITS.

Schema#

Identity instead of SERIAL#

There is no SERIAL/BIGSERIAL. An autoIncrement column becomes a bigint
identity column with DSQL's mandatory CACHE:
dialect.buildCreateTableSql('orders', {
  id: { type: DataTypes.INTEGER, autoIncrement: true, primaryKey: true },
}, { initialAutoIncrement: 1000 });
// CREATE TABLE "orders" ("id" BIGINT GENERATED BY DEFAULT AS IDENTITY
//   (CACHE 65536 START WITH 1000) PRIMARY KEY)
DSQL supports identity only on bigint, so an INTEGER column is widened —
pg returns int8 as a string unless you install a type parser. CACHE must
be 1 (strictly ordered, more coordination) or >= 65536 (unique, not ordered
across sessions).
AWS recommends random keys, which spread writes across DSQL's key range:
dialect.buildCreateTableSql('t', { id: dialect.uuidPrimaryKey() });
// CREATE TABLE "t" ("id" UUID DEFAULT gen_random_uuid() NOT NULL PRIMARY KEY)

Constraints#

PRIMARY KEY, UNIQUE, CHECK and foreign keys (supported since
DSQL added them, with NO ACTION/RESTRICT/CASCADE/SET NULL/SET DEFAULT)
are emitted inline. uniqueKeys become inline UNIQUE (...) constraints,
because DSQL's ALTER TABLE can only add a unique constraint USING INDEX.
A foreign key added later must be NOT VALID, then validated asynchronously:
dialect.buildAddForeignKeySql('items', 'order_id', 'orders', 'id');
// ALTER TABLE "items" ADD CONSTRAINT "items_order_id_fkey" FOREIGN KEY ("order_id")
//   REFERENCES "orders" ("id") NOT VALID
dialect.buildValidateConstraintSql('items', 'items_order_id_fkey');
// ALTER TABLE ASYNC "items" VALIDATE CONSTRAINT "items_order_id_fkey"

Indexes are always asynchronous#

A plain CREATE INDEX is a syntax error on DSQL. addIndex, createIndex and
createTable({ indexes }) all emit CREATE INDEX ASYNC, which returns a
job_id immediately:
const jobId = await dialect.createIndexAsync('orders', {
  name: 'orders_customer_idx',
  fields: ['customer_id', { column: 'created_at', nulls: 'LAST' }],
  include: ['status'],
  where: { status: 'open' },
});
// CREATE INDEX ASYNC "orders_customer_idx" ON "orders" ("customer_id",
//   "created_at" NULLS LAST) INCLUDE ("status") WHERE "status" = 'open'

await dialect.waitForJob(jobId);  // CALL sys.wait_for_job($1)
await dialect.getJob(jobId);      // the sys.jobs row
unique, nullsNotDistinct and ifNotExists are supported; USING,
CONCURRENTLY, raw expressions and raw-string predicates throw. At most 8 key
columns.

Sequences#

dialect.buildCreateSequenceSql({ name: 'order_no', cache: 65536, startWith: 101 });
// CREATE SEQUENCE "order_no" CACHE 65536 START WITH 101
cache is required. Temporary sequences are refused.

ALTER TABLE#

addColumn emits name and type only — a default, NOT NULL, key or reference
on the new column throws (DSQL's ADD COLUMN takes nothing else).
changeColumn throws: there is no ALTER COLUMN ... TYPE and no
SET NOT NULL. removeColumn and renameColumn are inherited.

The full refusal list#

Asked forWhat happens
SERIAL / BIGSERIAL typeRefused — use autoIncrement (identity) or UUID
ARRAY, INET, CIDR, MACADDR, RANGE columnsRefused — runtime-only or unsupported
HSTORE, VECTOR, PostGIS, CITEXTRefused — no extensions
temporary, partitionBy, inherit, tablespace on createTableRefused
Isolation other than REPEATABLE READRefused
SAVEPOINT (all three builders)Refused
lock: 'SHARE' / 'NO KEY UPDATE', NOWAIT, SKIP LOCKEDRefused — only FOR UPDATE / FOR KEY SHARE
truncate: true on deleteRefused — DELETE in batches
bulkInsert over 3,000 rowsRefused
createDatabaseSQL / dropDatabaseSQLRefused — one database per cluster
Triggers, extensions, materialized viewsRefused; has*/getExtensions report none
Policies / RLSRefused
Stored procedures / PL/pgSQLRefused — LANGUAGE SQL functions only
LISTEN / UNLISTEN / NOTIFYRefused
createEnumTypeRefused — no CREATE TYPE
All five partitioning entry pointsRefused
changeColumn, extras on addColumnRefused
What is supported and inherited unchanged: views, CREATE DOMAIN,
ON CONFLICT upserts, FOR UPDATE, foreign keys, COMMENT ON, and the whole
SELECT grammar.

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.
Capabilityauroradsql
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 columnrefused — Aurora DSQL cannot store pgvector types (it has no extensions) (column type 'VECTOR').
Array columnrefused — Aurora DSQL cannot store array columns (arrays exist only at query runtime — store the list as JSONB, or as rows in a child table) (column type 'ARRAY').
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/auroradsql.test.ts exercises the dialect with a mocked driver, so nothing touches a server.

See also#

Migrating from PostgreSQL to Aurora DSQL
Concurrency control in Aurora DSQL
Cluster quotas and database limits
Modified at 2026-10-04 00:40:16
Previous
Amazon Athena Dialect
Next
Amazon Aurora MySQL Dialect
Built with