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

Google Cloud Spanner Dialect

Overview#

Google Cloud Spanner is a fully-managed,
horizontally-scalable, strongly-consistent distributed SQL database. Unlike the
other distributed dialects in this codebase (cockroachdb is Postgres-wire,
tidb is MySQL-wire), Spanner is not wire-compatible with an existing
engine, so this dialect is a standalone Dialect implementation built on the
official @google-cloud/spanner driver rather than an extension of another
dialect.
PropertyValue
Dialect namespanner
Extendsnothing — implements Dialect directly
Driver@google-cloud/spanner
Cloud SDK@google-cloud/spanner
Default portnone — gRPC API
Local runtimethe Spanner emulator (emulator: true)
Key facts (from src/dialects/spanner/index.ts):
Dialect name is 'spanner'; the driver library is @google-cloud/spanner.
This dialect targets GoogleSQL, Spanner's native SQL dialect (backtick-quoted
identifiers, STRING(n)/INT64 types, @pN named parameters). It does not
target Spanner's PostgreSQL interface — connect() fails fast if the database
was provisioned with databaseDialect: POSTGRESQL (use the postgres dialect
for those). See GoogleSQL vs the PostgreSQL interface.
There is no local SQL port. The dialect authenticates via Google Application
Default Credentials (ADC) or an explicit service-account key and addresses a
database by project / instance / database IDs, not host/port.

Quick start#

Install#

$ npm install ts-prorm-orm @google-cloud/spanner
$ pnpm add ts-prorm-orm @google-cloud/spanner
$ yarn add ts-prorm-orm @google-cloud/spanner
$ bun add ts-prorm-orm @google-cloud/spanner

Connect#

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

export const db = new Prorm({
  dialect: 'spanner',
  dialectOptions: {
    projectId: 'my-project',
    instanceId: 'prod-instance',
    databaseId: 'app-db',
  },
});

Define a model#

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

const User = db.define('User', {
  id: { type: DataTypes.INTEGER(), primaryKey: true, autoIncrement: true },
  email: { type: DataTypes.STRING(255), allowNull: false, unique: true },
  name: { type: DataTypes.STRING(100) },
});

await db.sync(); // CREATE TABLE — see Generated SQL below

Query#

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

await User.create({ email: 'ada@example.com', name: 'Ada' });

const page = await User.findAll({
  where: { name: { [Op.like]: 'A%' } },
  order: [['id', 'ASC']],
  limit: 20,
  offset: 40,
});

Generated SQL#

Each block is the statement the model call above it hands the dialect's query(), captured with the driver stubbed out. The model layer inlines the values.

Create table#

db.sync() for the model in the Quick start:
CREATE TABLE

Insert, update and delete#

await User.create({ email: 'ada@example.com', name: 'Ada' });
await User.update({ name: 'Grace' }, { where: { email: 'ada@example.com' } });
await User.destroy({ where: { id: 1 } });

Upsert#

await User.upsert({ id: 1, email: 'ada@example.com', name: 'Ada Lovelace' });
upsert() also reads the row by primary key before and after the write, to return the instance.
[!WARNING] A plain INSERT
The engine has no conflict clause, so this upsert inserts and never updates an existing row.

Pagination#

await User.findAll({
  where: { name: { [Op.like]: 'A%' } },
  order: [['id', 'ASC']],
  limit: 20,
  offset: 40,
});

JSON#

[!NOTE] No JSON operator in the WHERE builder
DataTypes.JSON() maps to JSON, but this dialect's WHERE builder refuses Op.contains on it: Cannot render WHERE condition at meta.contains' is not implemented by its WHERE builder. The statement was not sent, because running it without the condition would match rows it should not.

Transaction#

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.
Type mapping for the portable descriptors: STRING → STRING(255), auto-increment INTEGER → INT64, BOOLEAN → BOOL, DATE → TIMESTAMP, UUID → STRING(36), JSON → JSON. The type comparison lines the major engines up side by side.

Connection#

Spanner-specific options are passed through dialectOptions:
import { Prorm } from 'ts-prorm-orm';

const db = new Prorm({
  dialect: 'spanner',
  dialectOptions: {
    projectId: 'my-gcp-project',   // omit to use ADC's default project
    instanceId: 'prod-instance',   // required
    databaseId: 'app-db',          // required
    // keyFilename: '/path/to/sa-key.json', // else falls back to ADC
  },
});

await db.connect();
For the Spanner emulator, pass emulator: true (defaults apiEndpoint to
localhost:9010) alongside skipDialectCheck: true.
SpannerDialectOptions (from the source):
instanceId / databaseId — required; identify the Spanner database.
projectId — GCP project; falls back to the ADC default project when omitted.
keyFilename / credentials — explicit service-account auth. When both are
omitted, the driver uses GOOGLE_APPLICATION_CREDENTIALS / ambient ADC (GCE,
GKE, Cloud Run metadata server).
apiEndpoint / emulator — override the endpoint / target the local emulator.
queryOptions — forwarded to every database.run() (e.g. optimizer version).
skipDialectCheck: true — skip the automatic GoogleSQL-dialect assertion done
on connect().

Distributed SQL & consistency model#

Spanner shards data across servers by primary-key ranges and rebalances splits
automatically — there is no user-facing PARTITION BY (all the
createPartitionedTable/createPartition/attachPartition methods throw).
Interleaved tables (below) are the closest Spanner-native tool for physical
co-location, but they solve co-location, not logical partitioning.
Every read-write transaction is externally consistent (TrueTime-ordered,
effectively stronger than SERIALIZABLE) by construction. There is no isolation-level
spectrum: startTransaction() accepts options.isolationLevel for interface
parity but ignores it with a warning rather than pretending to map it.

GoogleSQL vs the PostgreSQL interface#

Spanner exposes two SQL dialects. This implementation emits GoogleSQL only.
On connect() it calls assertGoogleSqlDialect(), which queries the Database
Admin API and throws an actionable error if the database is in POSTGRESQL
mode. Pass skipDialectCheck: true to bypass this, or call it manually:
await dialect.assertGoogleSqlDialect(); // throws if the DB is PostgreSQL-interface

Spanner-specific features#

Auto-generated keys — hotspot avoidance#

Spanner's docs explicitly discourage monotonically-increasing primary keys: they
concentrate every write on the single split holding the tail of the key range (a
hotspot). To keep the shared autoIncrement flag meaningful without reproducing
that anti-pattern, an autoIncrement column is mapped to a random, well-distributed
UUID (and a warning is logged):
await db.dialect.createTable('users', {
  id: { type: 'UUID', primaryKey: true, autoIncrement: true },
  name: { type: 'STRING', length: 100 },
});
Note GoogleSQL declares the primary key after the column-list parentheses,
not inline. A table with no primary key throws — mark a column primaryKey: true
or pass options.primaryKey: ['col', ...].

Bit-reversed sequences — ordered-but-distributed keys#

When you need a numeric key that is roughly ordered over time but still spread
across the keyspace, use a bit-reversed sequence instead of a plain counter:
await db.dialect.createBitReversedSequence('order_seq', { startWithCounter: 1 });

const id = await db.dialect.nextBitReversedSequenceValue('order_seq');
// or, as a column default / SQL fragment:
db.dialect.nextBitReversedSequenceValueSql('order_seq');
// => GET_NEXT_SEQUENCE_VALUE(SEQUENCE `order_seq`)

Interleaved tables#

INTERLEAVE IN PARENT physically co-locates a child table's rows with their
parent row (e.g. Orders under Customers) so point look-ups and joins across
the relationship stay within one storage split. The child's primary key must
include the parent's primary key as a prefix
:
await db.dialect.createTable('Customers', {
  CustomerId: { type: 'STRING', length: 36, primaryKey: true },
  Name: { type: 'STRING', length: 200 },
});

await db.dialect.createInterleavedTable(
  'Orders',
  'Customers', // parent
  {
    CustomerId: { type: 'STRING', length: 36 },
    OrderId: { type: 'STRING', length: 36 },
    Total: { type: 'NUMBER' },
  },
  { primaryKey: ['CustomerId', 'OrderId'], onDeleteCascade: true },
);

Covering (STORING) indexes and TTL#

addIndex's include option maps to Spanner's STORING (...) clause — a
covering index that duplicates listed columns so a lookup avoids a join back to
the base table. Row-TTL is expressed via a table-level row deletion policy:
await db.dialect.addIndex('Orders', 'idx_orders_total', ['Total'], {
  include: ['OrderId'], // STORING (`OrderId`)
});

await db.dialect.createTable('Events', {
  Id: { type: 'UUID', primaryKey: true, autoIncrement: true },
  CreatedAt: { type: 'DATE' }, // TIMESTAMP
}, {
  rowDeletionPolicy: { column: 'CreatedAt', olderThanDays: 30 },
});
// ... ROW DELETION POLICY (OLDER_THAN(`CreatedAt`, INTERVAL 30 DAY))
Spanner has no arbitrary partial-index WHERE predicate; passing where to
addIndex logs a warning and is ignored (the closest analogue is NULL_FILTERED).

Writes — SQL DML vs the Mutation API#

Spanner offers two write paths, and this dialect exposes both:
1.
SQL DML (INSERT/UPDATE/DELETE) — always run inside a read-write
transaction. query() transparently wraps single DML statements in an
auto-committing transaction, since Spanner has no autocommit single-statement
DML path.
2.
The Mutation API — the recommended, primary path for bulk/blind
writes: it skips SQL parsing/planning and batches into one commit.
// Mutation API (recommended for bulk / blind writes)
await db.dialect.mutationInsert('users', [{ id: 'a', name: 'Ada' }]);
await db.dialect.mutationUpdate('users', [{ id: 'a', name: 'Ada L.' }]);
await db.dialect.mutationUpsert('users', [{ id: 'a', name: 'Ada' }]); // insert-or-update by PK
await db.dialect.mutationDelete('users', ['a']);                      // delete by PK
await db.dialect.bulkInsert('users', records);                        // uses mutationInsert

Upsert — INSERT OR UPDATE INTO#

Spanner has no ON CONFLICT clause. The SQL upsert fallback emits GoogleSQL's
INSERT OR UPDATE INTO:
db.dialect.buildUpsertQuery('kv', { k: 'a', v: 1 });
Only the OR UPDATE variant is wired up (GoogleSQL also has OR IGNORE /
OR REPLACE, but there is no conflictAction option to select them). Prefer
mutationUpsert() over this SQL form for bulk writes.
GoogleSQL DML has no RETURNING clause — passing returning to
buildInsertQuery/buildUpdateQuery/buildDeleteQuery logs a warning and is
ignored. UPDATE and DELETE always require a WHERE (an always-true WHERE TRUE
is emitted when none is given; truncate maps to DELETE FROM t WHERE TRUE since
there is no TRUNCATE).

Transactions#

startTransaction/commitTransaction/rollbackTransaction bridge the driver's
callback-based database.runTransaction() into the imperative shape used
elsewhere. Contention surfaces as ABORTED (gRPC code 10); use isRetryableError()
to drive a retry loop (the driver also retries internally):
const tx = await db.dialect.startTransaction();
try {
  const spannerTx = (tx as any).spannerTransaction;
  await spannerTx.runUpdate({ sql: 'UPDATE `users` SET `name` = @p1 WHERE `id` = @p2', params: { p1: 'Ada', p2: 'a' } });
  await db.dialect.commitTransaction(tx);
} catch (err) {
  await db.dialect.rollbackTransaction(tx);
  if (db.dialect.isRetryableError(err)) { /* retry */ }
}
Read-only transactions (strong or stale/bounded-staleness reads) are a distinct
concept and are exposed separately, not through startTransaction():
const rows = await db.dialect.runReadOnlyTransaction(
  (run) => run('SELECT * FROM `users` WHERE `id` = @id', { id: 'a' }),
  { exactStaleness: { seconds: 15 } }, // lower-latency stale read
);
Spanner has no SAVEPOINT — the savepoint builders all throw.

Type mapping#

getDataTypeSql maps ORM type descriptors to GoogleSQL types:
ORM type descriptorGenerated SQL
{ key: 'STRING' } / { key: 'CHAR' }STRING(255) (or length)
{ key: 'TEXT' }STRING(MAX)
{ key: 'INTEGER' } / 'BIGINT'INT64
{ key: 'FLOAT' } / 'DOUBLE'FLOAT64
{ key: 'DECIMAL' }NUMERIC
{ key: 'BOOLEAN' }BOOL
{ key: 'DATE' }TIMESTAMP
{ key: 'DATEONLY' }DATE
{ key: 'BLOB' }BYTES(MAX) (or length)
{ key: 'UUID' }STRING(36)
{ key: 'JSON' } / 'JSONB'JSON
{ key: 'ENUM', values: [...] }STRING(MAX) CHECK (col IN (...))
{ key: 'ARRAY', type: <t> }ARRAY<t>
TIME, SET, RANGE, INET, CIDR, MACADDR, and HSTORE have no native
equivalent and fall back to STRING(MAX) (HSTORE → JSON) with a warning.
GEOMETRY throws — Spanner has no built-in geometry/geography type.

Not supported / caveats#

Methods that throw, because the underlying concept has no GoogleSQL analogue:
Schemas / namespaces — createSchema/dropSchema throw; GoogleSQL has no
CREATE SCHEMA. quoteTable(name, schema) ignores schema with a warning.
Databases via SQL — created/dropped through the Admin API
(instance.createDatabase() / database.delete()), not DDL.
Extensions, Foreign Data Wrappers, row-level security, stored procedures /
procedural SQL
— all throw; these are Postgres/relational concepts Spanner
lacks. Move procedural logic to the application layer.
CREATE USER / GRANT ... TO <user> — Spanner access is governed by Cloud
IAM plus GoogleSQL database roles. CREATE ROLE / DROP ROLE /
GRANT ROLE ... TO ROLE builders exist; per-user grants throw.
RENAME TABLE / RENAME COLUMN — not supported; add a new column/table,
backfill, drop the old one. Primary keys are fixed at CREATE TABLE time
(addConstraint with PRIMARY KEY throws).
DROP TABLE/DROP VIEW/DROP INDEX have no CASCADE — drop dependent
interleaved child tables and indexes explicitly first.
Other behavioral notes:
escape() and Date values. escape() has no column-type context, so a
JS Date is always emitted as a TIMESTAMP literal. GoogleSQL will reject
that for a DATE (DATEONLY) column. Pass a 'YYYY-MM-DD' string to
DATEONLY columns instead of a Date.
OFFSET requires LIMIT. GoogleSQL has no bare OFFSET n; when only an
offset is given, a very large LIMIT is emitted to satisfy the grammar.
Backups are an Admin API concept (createBackup/listBackups/getBackup/
deleteBackup/restoreDatabase), not BACKUP DATABASE DDL; these helpers
await the long-running operations to completion.
Window functions and (recursive) CTEs are standard GoogleSQL syntax and pass
straight through (buildWindowFunction, buildRecursiveCteQuery).

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.
Capabilityspanner
Transactions atomicyes
Savepointsno — a nested transaction() throws
Isolationup to SERIALIZABLE
Transaction modesread-only no; deferrable no; constraint deferral no
RETURNINGnot emitted; returning is accepted and ignored
Upserta plain INSERT: the engine has no conflict clause (see the page)
JSON columnJSON (JSONB → JSON)
Vector columnARRAY<FLOAT32>(vector_length=>3)
Array columnARRAY<INT64>
WHERE builder32 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 absent; createExtension() present

Testing#

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

Related reading#

All dialects — what each engine supports
Data types — how each type maps to this engine
Querying — how a FindOptions becomes SQL
Modified at 2026-10-04 00:40:16
Previous
Snowflake Dialect
Next
Spanner (PostgreSQL interface) Dialect
Built with