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

CrateDB Dialect

Overview#

CrateDB is a distributed SQL database built for search and
analytics over large volumes of structured and semi-structured data. It speaks the
PostgreSQL wire protocol (default port 5432) and is largely PG-compatible on
the client side.
PropertyValue
Dialect namecratedb
ExtendsPostgresDialect (postgres)
Driverpg
Cloud SDKnone
Default port5432
Local runtimeprorm db up --dialect cratedb (crate:5.8.3)
Because of that wire compatibility, the ORM's CrateDBDialect extends
PostgresDialect
and reuses the pg driver for connectivity and most query
building (SELECT / INSERT / UPDATE / DELETE). It overrides only the surface where
CrateDB genuinely differs from PostgreSQL:
CREATE TABLE generation (distribution/partitioning clauses + CrateDB type mapping)
Type mapping (getDataTypeSql)
No foreign keys
No standalone CREATE INDEX (all columns are auto-indexed; fulltext indexes are
declared inline at CREATE TABLE)
No column/table renames
An extra ON CONFLICT ... DO NOTHING insert variant
The dialect reports its identity accordingly:
dialect.name;    // 'cratedb'
dialect.library; // 'pg'  (inherited from PostgresDialect)
Source: cratedb,
base: postgres.

Quick start#

Install#

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

Connect#

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

export const db = new Prorm({
  dialect: 'cratedb',
  host: 'localhost',
  database: 'doc',
  username: 'crate',
});
import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'cratedb',
  url: 'cratedb://crate@localhost:5432/doc',
});
A URL is folded into host, port, database, username and password before the dialect is built; any of those passed alongside it wins.

Define a model#

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

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

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

Query#

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

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

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

Generated SQL#

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

Create table#

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

Insert, update and delete#

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

Upsert#

await User.upsert({ id: 1, email: 'ada@example.com', name: 'Ada Lovelace' });
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#

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
Nested transactions need savepoints, and cratedb has none. Run the work in a single transaction, or restructure it so nothing nests.
Type mapping for the portable descriptors: STRING → TEXT, auto-increment INTEGER → INTEGER, BOOLEAN → BOOLEAN, DATE → TIMESTAMP, UUID → TEXT, JSON → OBJECT. The type comparison lines the major engines up side by side.

Connection#

CrateDB is PG-wire compatible, so CrateDBDialectOptions is just the Postgres option
set. The constructor forwards { port: 5432, ...config } to the Postgres base, so the
default port stays 5432 even though you can override it.
import { Prorm } from 'ts-prorm-orm';

const prorm = new Prorm({
  dialect: 'cratedb',
  host: 'localhost',
  port: 5432, // default; PG-wire compatible
  username: 'crate',
  password: '',
  database: 'doc',
});
The Postgres base defaults host to 'localhost' and port to 5432 when omitted.
Connection uses the standard pg pool (max: 20, idleTimeoutMillis: 30000,
connectionTimeoutMillis: 2000 by default, all inherited from the Postgres dialect).

Row locks and PostgreSQL-only operators#

The dialect extends PostgresDialect, but the PostgreSQL-only parts of its
SELECT are not CrateDB SQL, so they are rendered natively or refused.
CrateDB has no row-level locking, so any lock option is refused:
CrateDB has no row-level locking, so `lock` cannot be honoured. Remove the `lock` option; a lock the caller believes it holds but does not is worse than an error.
The PostgreSQL JSON, array, range and full-text operators (Op.contains as
@>, Op.overlap as &&, ?, range operators, @@) are refused with an
UnsupportedWhereError, and the statement is not sent:
Cannot render WHERE condition at tags.$contains for cratedb: the operator '$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.
[!NOTE]
Before 4.9.2 this dialect sent PostgreSQL's FOR SHARE / SKIP LOCKED
clauses and the @> / && operators unchanged, and the server rejected
them.

What differs from Postgres#

CrateDBDialect extends PostgresDialect (postgres) and
overrides 66 of its methods (Object.getOwnPropertyNames(CrateDBDialect.prototype),
computed by the scratch test); everything else is inherited unchanged.
AreaOverridden
DML buildersbuildInsertQuery, formatDefaultValue
TypesbuildObjectTypeSql, canonicalTypeSql, createEnumType, dropType, ensureEnumTypes, getCrateColumnDefinitionSql, getDataTypeSql, legacyCrateStringTypeSql, legacyCrateTypeSql, mapNativeType, unsupportedType
DDL and schemaaddColumn, addConstraint, addForeignKey, addIndex, attachPartition, buildCreateTableSQL, createConstraint, createDomain, createForeignDataWrapper, createForeignServer, createForeignTable, createFulltextIndex, createIndex, createMaterializedView, createPartition, createPartitionedTable, createPolicy, createSequence, createSpatialIndex, createStoredProcedure, createTable, createTrigger, createUserMapping, detachPartition, disableRLS, dropDomain, dropForeignDataWrapper, dropForeignServer, dropIndex, dropMaterializedView, dropPartition, dropPolicy, dropSequence, dropStoredProcedure, dropTrigger, dropUserMapping, enableRLS, refreshMaterializedView, removeIndex, renameColumn, renameTable
IntrospectionhasMaterializedView, hasPolicy, hasSequence, hasStoredProcedure, hasTrigger, showMaterializedViews
OtherbuildCrateConstraintSql, executeStoredProcedure, formatSettingValue, lockClauseSpec, nextSequenceValue, unsupportedWhereOperators

CrateDB-specific features#

CrateDB's CREATE TABLE clauses are passed via CrateDBTableOptions, which is combined
with the shared TableOptions (an intersection type, since these options are not part
of every dialect):
interface CrateDBTableOptions {
  clusteredInto?: number;      // CLUSTERED INTO n SHARDS
  shards?: number;             // alias for clusteredInto
  clusteredBy?: string;        // CLUSTERED BY (col)
  partitionedBy?: string | string[]; // PARTITIONED BY (col, ...)
  with?: Record<string, string | number | boolean>; // WITH ( key = value, ... )
  fulltextIndexes?: Array<{ name: string; fields: string[]; analyzer?: string }>;
}

Clause order#

After the column list, buildCreateTableSQL emits clauses in CrateDB's required order:
1.
PARTITIONED BY (col, ...)
2.
CLUSTERED [BY (col)] INTO n SHARDS
3.
WITH ( key = value, ... )

Sharding, partitioning, and settings#

const columns = {
  id:      { type: { key: 'BIGINT' }, primaryKey: true },
  day:     { type: { key: 'STRING' } },
  payload: {
    type: {
      key: 'OBJECT',
      columnPolicy: 'DYNAMIC',
      fields: { tags: { key: 'ARRAY', type: { key: 'STRING' } } },
    },
  },
};

dialect.buildCreateTableSQL('events', columns, {
  partitionedBy: 'day',
  clusteredBy: 'id',
  clusteredInto: 6,
  with: { number_of_replicas: '1', '"refresh_interval"': 1000 },
});
Generated SQL (clause order: PARTITIONED BY, then CLUSTERED, then WITH):
Notes verified against the source and tests:
Identifiers are double-quoted (inherited escapeId).
CLUSTERED BY (col) can be omitted — clusteredInto (or shards) alone yields a bare
CLUSTERED INTO n SHARDS:
dialect.buildCreateTableSQL('metrics', { id: { type: { key: 'BIGINT' } } }, { clusteredInto: 4 });
// ... CLUSTERED INTO 4 SHARDS   (no "CLUSTERED BY")
WITH values: string values are single-quoted (embedded quotes doubled), while
numeric/boolean values are emitted bare. Keys are emitted verbatim, so a
pre-quoted key such as '"refresh_interval"' is preserved as "refresh_interval".

OBJECT columns#

OBJECT (and JSON/JSONB/HSTORE) types with declared sub-columns emit
OBJECT(POLICY) AS (col type, ...); the policy defaults to DYNAMIC. With no
sub-columns, a bare OBJECT is emitted.
dialect.getDataTypeSql({
  key: 'OBJECT',
  columnPolicy: 'DYNAMIC',
  fields: { name: { key: 'STRING' }, age: { key: 'INTEGER' } },
});
// OBJECT(DYNAMIC) AS ("name" TEXT, "age" INTEGER)

ARRAY columns#

CrateDB uses ARRAY(type), not Postgres's type[]:
dialect.getDataTypeSql({ key: 'ARRAY', type: { key: 'INTEGER' } }); // ARRAY(INTEGER)
dialect.getDataTypeSql({ key: 'ARRAY', type: { key: 'STRING' } });  // ARRAY(TEXT)

Fulltext indexes#

CrateDB has no standalone CREATE INDEX statement — the only user-defined indexes
are fulltext indexes, and they must be declared inline at CREATE TABLE via
fulltextIndexes. Each entry emits one INDEX name USING FULLTEXT (cols) [WITH (analyzer = '...')]
column.
dialect.buildCreateTableSQL('docs', columns, {
  clusteredInto: 4,
  fulltextIndexes: [{ name: 'ft_body', fields: ['title', 'body'], analyzer: 'english' }],
});
emits (inside the column list):
Without an analyzer:
Related methods throw rather than emit invalid SQL:
addIndex, createIndex, removeIndex, dropIndex — throw "no CREATE INDEX"
(all columns are auto-indexed).
createFulltextIndex — throws, directing you to declare it at CREATE TABLE.
createSpatialIndex — throws (GEO_SHAPE indexes are inline at CREATE TABLE).
createTable with a generic options.indexes array logs a console.warn and ignores
them (it does not emit CREATE INDEX).

Renames#

CrateDB cannot rename columns or tables. renameColumn and renameTable both throw.
addColumn is supported and emits ALTER TABLE ... ADD COLUMN ... using CrateDB's type
mapping (dropping any FK reference).

CRUD#

The standard SELECT / INSERT / UPDATE / DELETE builders are inherited from the Postgres
base and produce valid CrateDB SQL. Identifiers are double-quoted and values are
parameterized with $1, $2, ... placeholders.
dialect.buildInsertQuery('users', { id: 1, name: 'Ada' });
// INSERT INTO "users" ("id", "name") VALUES ($1, $2)   values: [1, 'Ada']

dialect.buildSelectQuery({ tableName: 'users', attributes: ['id', 'name'] });
// SELECT "id", "name" FROM "users"

dialect.buildUpdateQuery('users', { name: 'Bob' }, { id: 1 });
// UPDATE "users" SET "name" = $1 WHERE ...

dialect.buildDeleteQuery('users', { id: 1 });
// DELETE FROM "users" WHERE ...

ON CONFLICT ... DO UPDATE (upsert)#

Inherited from the Postgres base unchanged — its output is valid CrateDB SQL:
dialect.buildUpsertQuery(
  'users',
  { id: 1, name: 'Ada', email: 'a@x.io' },
  { conflictFields: ['id'], updateOnDuplicate: ['name', 'email'] },
);
// INSERT INTO "users" ("id", "name", "email") VALUES (...)
//   ON CONFLICT ("id") DO UPDATE SET "name" = excluded."name", "email" = excluded."email"

ON CONFLICT ... DO NOTHING (CrateDB override)#

CrateDBInsertOptions adds onConflictDoNothing. Unlike DO UPDATE, DO NOTHING may
omit the conflict target. RETURNING (if requested) is appended after DO NOTHING.
// With a conflict target:
dialect.buildInsertQuery('users', { id: 1, name: 'Ada' },
  { onConflictDoNothing: true, conflictFields: ['id'] });
// INSERT INTO "users" ("id", "name") VALUES ($1, $2) ON CONFLICT ("id") DO NOTHING

// Without a conflict target:
dialect.buildInsertQuery('users', { id: 1 }, { onConflictDoNothing: true });
// INSERT INTO "users" ("id") VALUES ($1) ON CONFLICT DO NOTHING

// With RETURNING (placed after DO NOTHING):
dialect.buildInsertQuery('users', { id: 1 },
  { onConflictDoNothing: true, conflictFields: ['id'], returning: ['id'] });
// INSERT INTO "users" ("id") VALUES ($1) ON CONFLICT ("id") DO NOTHING RETURNING "id"

Foreign keys are omitted#

CrateDB has no foreign-key support, so both column-level references and table-level
FOREIGN KEY constraints are dropped from generated DDL rather than emitted. The
column itself is still created — only the FK reference is removed:
dialect.buildCreateTableSQL('events', {
  id:       { type: { key: 'BIGINT' }, primaryKey: true },
  owner_id: { type: { key: 'BIGINT' }, references: { table: 'users', field: 'id' } },
}, {
  clusteredInto: 6,
  constraints: [{ type: 'FOREIGN KEY', fields: ['owner_id'], references: { table: 'users', field: 'id' } }],
});
// The output contains "owner_id" BIGINT but NO "FOREIGN KEY" / "REFERENCES".
The async FK helpers reject explicitly rather than emit unsupported DDL:
addForeignKey — throws "CrateDB does not support foreign keys."
addConstraint / createConstraint — throw for FOREIGN KEY, but delegate other
constraint types (UNIQUE, CHECK, PRIMARY KEY) to the Postgres base.

PRIMARY KEY (with routing-column caveat)#

PRIMARY KEY is preserved, both as a column modifier ("id" BIGINT PRIMARY KEY) and as a
table constraint (PRIMARY KEY (fields)).
Caveat: In CrateDB, a PRIMARY KEY must include every routing/clustered/partitioned
column. The dialect does not validate or rewrite the PRIMARY KEY to enforce this —
it is the caller's responsibility to make the primary key include the clusteredBy /
partitionedBy columns.

Type mapping#

getDataTypeSql overrides the Postgres mapping to emit CrateDB-native types. It accepts
both structured DataType objects ({ key: '...' }) and cross-dialect type strings.
Structured types (dt.key):
ORM type (key)CrateDB SQL
STRING, CHAR, TEXT, ENUM, UUID, INET, CIDR, MACADDRTEXT
INTEGERINTEGER
BIGINTBIGINT
FLOAT, DOUBLE, DECIMALDOUBLE PRECISION
BOOLEANBOOLEAN
DATE, DATEONLY, TIMETIMESTAMP
JSON, JSONB, HSTORE, OBJECTOBJECT / OBJECT(POLICY) AS (...)
ARRAYARRAY(base)
GEOMETRY, GEOGRAPHY, GEO_POINTGEO_POINT
GEO_SHAPEGEO_SHAPE
VIRTUAL'' (no column emitted)
unknown / non-objectTEXT
String inputs (cross-dialect / PG type strings) are normalized:
Input string (regex)CrateDB SQL
DATETIME[(n)]TIMESTAMP
VARCHAR, CHARACTER VARYING, CHARACTER, CHAR, STRING, NVARCHAR, NCHAR, TEXT, CLOBTEXT
JSON / JSONB / HSTOREOBJECT
UUIDTEXT
SERIAL / BIGSERIAL / SMALLSERIALBIGINT
REAL, FLOAT, NUMERIC, DECIMAL, DOUBLE [PRECISION]DOUBLE PRECISION
TIMESTAMP, TIMESTAMPTZ, DATE, TIME [(n)]TIMESTAMP
any other stringreturned as-is
Examples verified in tests: 'VARCHAR(255)' → TEXT, 'SERIAL' → BIGINT,
'NUMERIC(10,2)' → DOUBLE PRECISION, 'TIMESTAMPTZ' → TIMESTAMP, 'JSONB' → OBJECT,
'DATETIME' → TIMESTAMP.

Not-yet-verified#

SQL-generation verified (covered by unit tests, no database required —
tests/dialects/cratedb.test.ts and tests/dialects/cratedb-crud.test.ts build SQL
synchronously and never call connect()):
getDataTypeSql mappings (structured and string inputs), including OBJECT(...),
ARRAY(...), and geo types.
buildCreateTableSQL output: clause order (PARTITIONED BY → CLUSTERED → WITH),
CLUSTERED [BY] INTO n SHARDS, WITH settings formatting, fulltext INDEX, PRIMARY KEY
preservation, and FK omission.
INSERT / UPSERT / SELECT / UPDATE / DELETE string output, including ON CONFLICT ... DO NOTHING (with/without target, with RETURNING).
The "unsupported" methods (addIndex, createIndex, createFulltextIndex,
createSpatialIndex, removeIndex, dropIndex, addForeignKey, renameColumn,
renameTable, and FK dispatch in addConstraint/createConstraint) throw as expected.
Not verified against a live CrateDB — the following would require an actual running
CrateDB server and are not exercised by the current tests:
Actual connectivity via the pg driver against a CrateDB node (the dialect assumes
PG-wire compatibility; no integration test connects).
Runtime execution / acceptance of the generated DDL and DML by CrateDB (e.g. whether a
given PRIMARY KEY satisfies CrateDB's routing-column requirement, analyzer validity,
OBJECT policy semantics, refresh_interval / number_of_replicas behavior).
createTable, addColumn, and other async methods that issue query(...) — only the
synchronous SQL they build (or the errors they throw) is tested, not execution.

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.
Capabilitycratedb
Transactions atomicyes
Savepointsno — a nested transaction() throws
Isolationup to SERIALIZABLE
Transaction modesread-only yes; deferrable yes; constraint deferral yes
RETURNINGRETURNING on INSERT
UpsertINSERT … ON CONFLICT (…) DO UPDATE
JSON columnOBJECT (JSONB → OBJECT)
Vector columnFLOAT_VECTOR(3)
Array columnARRAY(INTEGER)
WHERE builder46 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/cratedb.test.ts exercises the dialect with a mocked driver, so nothing touches a server. A live instance: prorm db up --dialect cratedb (see Local databases).

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
Azure Cosmos DB for PostgreSQL Dialect
Next
Cloudflare D1 Dialect
Built with