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

RisingWave Dialect

Overview#

RisingWave is a streaming database: data arrives
through SOURCEs and connector-backed TABLEs (Kafka, Kinesis, Pulsar,
Postgres/MySQL CDC, ...), is transformed by MATERIALIZED VIEWs that are
maintained incrementally, and leaves through SINKs and SUBSCRIPTIONs.
It speaks the PostgreSQL frontend/backend wire protocol on port 4566, so
RisingWaveDialect extends PostgresDialect and reuses the pg driver,
connection pooling, escaping, $n parameter binding, double-quoted identifier
escaping, buildWhereClause, buildOrderClause and buildSelectQuery
unchanged. Reading a materialized view with findAll-shaped options needs no
hand-written SQL.
PropertyValue
Dialect namerisingwave
ExtendsPostgresDialect
Driverpg
Default port4566 (not 5432)
Cloud SDKnone
Local runtimeprorm db up --dialect risingwave (risingwavelabs/risingwave:v2.0.1)
The class overrides the inherited readonly name: string = 'postgres' with
'risingwave'; library stays 'pg' — the wire and the driver genuinely are
PostgreSQL's (d.library === 'pg' is asserted directly in the test suite).
The dialect is registered with Prorm (SqlDialect.RisingWave in
src/dialect-names.ts, wired to RisingWaveDialect in
src/dialects/loaders.ts, default port 4566 in src/connection-url.ts), so it
can be selected by name:
import { Prorm } from 'ts-prorm-orm';

const db = new Prorm({
  dialect: 'risingwave',
  host: 'localhost',
  // port defaults to 4566, not 5432 — inheriting Postgres's default would
  // make every connection fail against a healthy deployment
  username: 'root', // a local RisingWave's default user
  database: 'dev', // a local RisingWave's default database
});
It can also be constructed directly:

const d = new Prorm({
  dialect: 'risingwave',
  host: 'localhost',
  username: 'root',
  database: 'dev',
});
// or: const d = createRisingWaveDialect({ ... });

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: 'risingwave',
  host: 'localhost',
  database: 'dev',
  username: 'root',
});
import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'risingwave',
  url: 'risingwave://root@localhost:4566/dev',
});
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, allowNull: false },
  email: { type: DataTypes.STRING(255), allowNull: false },
  name: { type: DataTypes.STRING(100) },
  meta: { type: DataTypes.JSONB() },
});

await db.sync(); // CREATE TABLE — see Generated SQL below
The key has no autoIncrement: the engine has no sequence or identity column the dialect will emit, so the application supplies id. email is not declared unique: the engine has no enforced UNIQUE constraint. meta is JSONB, which the containment query below needs.

Query#

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

await User.create({ id: 1, 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({ id: 1, email: 'ada@example.com', name: 'Ada' });
await User.update({ name: 'Grace' }, { where: { email: 'ada@example.com' } });
await User.destroy({ where: { id: 1 } });

Upsert#

[!WARNING] No upsert
RisingWave's INSERT has no ON CONFLICT clause — conflict handling is a property of the table (CREATE TABLE ... ON CONFLICT OVERWRITE | DO NOTHING | DO UPDATE IF NOT NULL; pass onConflict to createTable). On a table with a primary key the default is OVERWRITE, so a plain INSERT already replaces the row with that key.

Pagination#

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

JSON#

Containment on the meta column:
import { Op } from 'ts-prorm-orm';

await User.findAll({ where: { meta: { [Op.contains]: { plan: 'pro' } } } });

Transaction#

[!CAUTION] No writes in a transaction
RisingWave transactions are read-only (START TRANSACTION READ ONLY), so this write cannot run inside one. Run it without transaction: RisingWave applies each write on its own, and has no multi-statement atomic writes.
Type mapping for the portable descriptors: STRING → VARCHAR, auto-increment INTEGER → refused, BOOLEAN → BOOLEAN, DATE → TIMESTAMP, UUID → refused, JSON → JSONB. The type comparison lines the major engines up side by side.

Connection#

RisingWaveDialectOptions is PostgresDialectOptions unchanged — same pg
option surface, only the default port differs.
OptionDefaultNotes
hostinherited from PostgresDialect
port4566RISINGWAVE_DEFAULT_PORT; overridable (`new Prorm({
dialect: 'risingwave',
port: 1234,
})`)
usernameinheriteda local RisingWave's default user is root
passwordinherited
databaseinheriteda local RisingWave's default database is dev

What differs from Postgres#

RisingWaveDialect extends PostgresDialect (postgres) and
overrides 82 of its methods (Object.getOwnPropertyNames(RisingWaveDialect.prototype),
computed by the scratch test); everything else is inherited unchanged.
AreaOverridden
Connection and executionlisten, notify, query, startTransaction, unlisten
DML buildersbuildInsertQuery, buildUpsertQuery, buildWindowedAggregateQuery, formatDefaultValue
TypesbuildAddColumnSql, buildColumnSql, canonicalTypeSql, createEnumType, ensureEnumTypes, getDataTypeSql, mapNativeType, unsupportedType
DDL and schemaaddColumn, addForeignKey, addIndex, attachPartition, buildCreateIndexSql, buildCreateMaterializedViewSql, buildCreateSinkSql, buildCreateSourceSql, buildCreateSubscriptionSql, buildCreateTableSql, buildCreateVectorIndexSql, buildCreateWindowedMaterializedViewSql, buildDropSubscriptionSql, changeColumn, createDomain, createExtension, createIndex, createMaterializedView, createPartition, createPartitionedTable, createPolicy, createSavepointSQL, createSequence, createSink, createSource, createStoredProcedure, createTable, createTrigger, detachPartition, disableRLS, dropExtension, dropPartition, dropPolicy, dropSequence, dropStoredProcedure, dropTrigger, enableRLS, refreshMaterializedView, renameColumn
IntrospectionassertIndexOptionsSupported, getExtensions, hasExtension, hasPolicy, hasSequence, hasStoredProcedure, hasTrigger, tablePrimaryKey
OtherbuildCloseCursorSql, buildDeclareSubscriptionCursorSql, buildFetchSubscriptionCursorSql, interval, nextSequenceValue, partitionRefusal, releaseSavepointSQL, renderConnector, renderFormat, renderProperties, renderWatermark, renderWindowedAggregate, rlsRefusal, rollbackToSavepointSQL, savepointRefusal, sequenceRefusal, structFieldName, upsertRefusal

What RisingWave has that PostgreSQL does not#

Data types#

getDataTypeSql implements PostgreSQL's core scalar types with two
restrictions and no extension types:
Model typeRisingWave SQLNote
STRING / TEXT / CHAR / ENUMVARCHARno length; no enum type, so an enum column is a plain varchar
DECIMALNUMERICno precision/scale
JSONJSONBRisingWave implements jsonb only
DATETIMESTAMPthe ORM's DATE is a timestamp; RisingWave's timestamp takes no precision
TIMETIME
VECTORVECTOR(n)needs dimensions/length; throws without one
UUID, HSTORE, CITEXT, PostGIS types (GEOMETRY, POINT, ...), INET/CIDR/MACADDR, RANGEthrowsextension types; RisingWave has no extensions
autoIncrement on any typethrowsno sequences, so no SERIAL
Everything else falls through to PostgresDialect.getDataTypeSql.

CREATE TABLE — primary key, watermark, conflict behaviour, connectors#

d.buildCreateTableSql(
  'events',
  { id: { type: DataTypes.BIGINT, primaryKey: true }, ts: { type: DataTypes.DATE } },
  { watermark: { column: 'ts', delay: '5 seconds' }, onConflict: 'do_update_if_not_null' },
);
A connector table with APPEND ONLY and a wire format:
d.buildCreateTableSql('t', { a: { type: DataTypes.BIGINT } }, {
  appendOnly: true,
  connector: { connector: 'kafka', topic: 't', 'properties.bootstrap.server': 'k:9092' },
  format: { format: 'PLAIN', encode: 'JSON' },
});
Grammar rules enforced: PRIMARY KEY may be declared inline (single column) or
as one table-level clause (composite key, or a PRIMARY KEY table
constraint — the only table constraint accepted); APPEND ONLY and a primary
key are mutually exclusive; ON CONFLICT / WITH VERSION COLUMN require a
primary key; WITH VERSION COLUMN only combines with OVERWRITE or
DO UPDATE IF NOT NULL; FORMAT ... ENCODE ... requires connector.
createTable also runs COMMENT ON TABLE/COMMENT ON COLUMN for any
comments and creates options.indexes through addIndex.

ALTER TABLE ... ADD COLUMN#

d.buildAddColumnSql('t', 'c', { type: DataTypes.STRING, defaultValue: 'x' });
// ALTER TABLE "t" ADD COLUMN "c" VARCHAR DEFAULT 'x'

Sources — CREATE SOURCE#

d.buildCreateSourceSql({
  name: 'clicks',
  ifNotExists: true,
  columns: { user_id: { type: DataTypes.BIGINT }, ts: { type: DataTypes.DATE } },
  watermark: { column: 'ts', delay: '5 seconds' },
  with: { connector: 'kafka', topic: 'clicks', 'properties.bootstrap.server': 'k:9092' },
  format: { format: 'PLAIN', encode: 'AVRO', options: { 'schema.registry': 'http://r:8081' } },
});
A source declares no defaults (a column defaultValue throws), and
FORMAT UPSERT requires primaryKey. WITH (...) property keys are
validated against a dotted-identifier pattern and every value is emitted as an
escaped string literal — WITH TTL on a watermark is refused for sources
(tables only).

Sinks — CREATE SINK#

FROM an existing object, or AS a structured windowed aggregate — exactly
one of the two is required:
d.buildCreateSinkSql({
  name: 'out', ifNotExists: true,
  as: {
    from: 'clicks', timeColumn: 'ts',
    window: { type: 'tumble', size: '1 minute' },
    aggregates: [{ fn: 'count', as: 'n' }],
    emitOnWindowClose: true,
  },
  with: { connector: 'blackhole' },
});

Time windows — TUMBLE / HOP / EMIT ON WINDOW CLOSE#

buildWindowedAggregateQuery builds a bound read (filter values as $n);
buildCreateWindowedMaterializedViewSql builds the DDL form (filter values
escaped inline, since DDL carries no parameter list):
d.buildWindowedAggregateQuery({
  from: 'clicks', timeColumn: 'ts',
  window: { type: 'tumble', size: '1 minute' },
  groupBy: ['page'],
  aggregates: [
    { fn: 'count', as: 'views' },
    { fn: 'count', column: 'user_id', distinct: true, as: 'users' },
  ],
  where: { country: 'NZ' },
});
d.buildWindowedAggregateQuery({
  from: 'clicks', timeColumn: 'ts',
  window: { type: 'hop', hop: '1 minute', size: '5 minutes', offset: '30 seconds' },
  aggregates: [{ fn: 'sum', column: 'amount', as: 'total' }],
});
Supported aggregates: count, sum, avg, min, max (count() with no
column counts rows; every other aggregate requires a column). Session windows
are refused — RisingWave's session window is a window-function frame
(SESSION WITH GAP), not a table function like TUMBLE/HOP.
buildCreateWindowedMaterializedViewSql wraps the same rendering in
CREATE MATERIALIZED VIEW [IF NOT EXISTS] name AS ....

Materialized views — always current, never refreshed#

buildCreateMaterializedViewSql(options: MaterializedViewOptions) builds the
shared-shape form (query is raw SQL text):
d.buildCreateMaterializedViewSql({ name: 'mv', query: 'SELECT 1', ifNotExists: true });
// CREATE MATERIALIZED VIEW IF NOT EXISTS "mv" AS SELECT 1
replace: true and withData: false both throw (see Refused table below).
createMaterializedView also runs COMMENT ON MATERIALIZED VIEW for a
comment.

Subscriptions — a retained changefeed#

d.buildCreateSubscriptionSql({ name: 'sub', from: 'mv', retention: '1D' });
// CREATE SUBSCRIPTION "sub" FROM "mv" WITH (retention = '1D')

d.buildDropSubscriptionSql('sub', { ifExists: true });
// DROP SUBSCRIPTION IF EXISTS "sub"

d.buildDeclareSubscriptionCursorSql('c', 'sub', 'full');
// DECLARE "c" SUBSCRIPTION CURSOR FOR "sub" FULL

d.buildDeclareSubscriptionCursorSql('c', 'sub', 1717000000000);
// DECLARE "c" SUBSCRIPTION CURSOR FOR "sub" SINCE 1717000000000

d.buildFetchSubscriptionCursorSql('c', { count: 100, timeout: '1s' });
// FETCH 100 FROM "c" WITH (timeout = '1s')

d.buildCloseCursorSql('c');
// CLOSE "c"
Cursor start accepts 'full' (current snapshot then every change),
'now'/'proctime' (SINCE now()/SINCE proctime()), 'begin'
(SINCE begin()), or a non-negative integer/bigint rw_timestamp
(SINCE <n>) — anything else throws. Rows fetched from a cursor carry the
object's columns plus op (Insert, UpdateInsert, UpdateDelete,
Delete) and rw_timestamp.

Indexes#

d.buildCreateIndexSql('orders', {
  name: 'idx', ifNotExists: true,
  columns: ['customer', { name: 'ts', order: 'DESC' }],
  include: ['total'],
  distributedBy: ['customer'],
});
INCLUDE stores extra columns so a lookup need not go back to the table;
DISTRIBUTED BY chooses how index rows are spread across compute nodes.
Vector indexes (technical preview, v2.6+; index append-only inputs only):
d.buildCreateVectorIndexSql('docs', {
  name: 'vi', column: 'emb', method: 'hnsw', distanceType: 'cosine',
  include: ['id'], params: { m: 16, ef_construction: 64 },
});
method must be flat or hnsw; distanceType must be l1, l2,
inner_product or cosine; params keys are validated as identifiers and
values must be finite numbers.

Transactions — read-only snapshots#

await d.startTransaction();
// START TRANSACTION READ ONLY
RisingWave transactions read from a consistent snapshot; there is no
read-write transaction and no isolation level to choose, so
startTransaction({ isolationLevel: ... }) throws instead of silently
starting a different kind of transaction than requested.
A write (INSERT, UPDATE, DELETE, DDL, or a WITH that writes) passed a
transaction is refused with a TransactionError before it is sent, because
the server would reject it inside READ ONLY. Run writes without
transaction; RisingWave applies each one on its own. Before 4.9.2 the write
was sent and failed on the server.

Refused, by name#

CallWhy
getDataTypeSql for UUID, HSTORE, CITEXT, PostGIS types, INET/CIDR/MACADDR, RANGEextension types; RisingWave has no extensions
getDataTypeSql with autoIncrementno sequences, so no SERIAL
column uniqueno UNIQUE constraint — make it the primary key or dedupe in a materialized view
column referencesno FOREIGN KEY — join in a materialized view instead
column autoIncrementno sequences
a table constraint other than PRIMARY KEY (UNIQUE, FOREIGN KEY, CHECK)tables carry PRIMARY KEY, NOT NULL, DEFAULT only
createTable with temporary, partitionBy, uniqueKeys, inherit, tablespaceno temp tables, partitioning, unique keys, inheritance or tablespaces
createTable with both column-level primaryKey and a PRIMARY KEY constraintkey declared twice
appendOnly + a primary keyappend-only tables never overwrite, so a key makes no sense
onConflict/versionColumn on a table with no primary keyON CONFLICT is keyed on the primary key
versionColumn with onConflict: 'do_nothing'WITH VERSION COLUMN only combines with OVERWRITE/DO UPDATE IF NOT NULL
format without connectorFORMAT/ENCODE apply to connector tables
changeColumnALTER COLUMN TYPE only extends struct types
renameColumnRisingWave's ALTER TABLE renames the table or swaps two tables, not a column
addForeignKeyno foreign keys
index uniqueuniqueness comes from the table's primary key
index where (partial)no partial indexes — index a materialized view that carries the filter
index concurrentlyindex creation already backfills as a streaming job without blocking writes
index expressionindex a column, add a generated column for the expression if needed
index using/typeordinary indexes take no USING; use buildCreateVectorIndexSql for similarity search
buildCreateMaterializedViewSql with replace: trueno CREATE OR REPLACE MATERIALIZED VIEW
buildCreateMaterializedViewSql with withData: falseno WITH NO DATA — a view backfills and is maintained from creation
refreshMaterializedViewno REFRESH MATERIALIZED VIEW — always current
buildUpsertQuery / buildInsertQuery(..., { upsert: true })no ON CONFLICT clause on INSERT; conflict handling is a table property (onConflict on createTable)
startTransaction({ isolationLevel })transactions are read-only snapshots; no isolation levels
createSavepointSQL / releaseSavepointSQL / rollbackToSavepointSQLno SAVEPOINT
listen / unlistenno LISTEN/UNLISTEN — points at CREATE SUBSCRIPTION
notifyno NOTIFY — points at CREATE SINK
createSequence / dropSequence / nextSequenceValueno sequences (hasSequence() resolves false)
createTrigger / dropTriggerno triggers — a materialized view or sink is the declarative equivalent (hasTrigger() resolves false)
createPolicy / dropPolicy / enableRLS / disableRLSno row-level security (hasPolicy() resolves false)
createStoredProcedure / dropStoredProcedureno stored procedures — only CREATE FUNCTION UDFs (hasStoredProcedure() resolves false)
createExtension / dropExtensionno extensions (getExtensions() resolves [], hasExtension() resolves false)
createPartitionedTable / createPartition / attachPartition / detachPartition / dropPartitionno table partitioning — data is distributed by primary key; expire old rows with a watermark WITH TTL
createEnumTypeno CREATE TYPE ... AS ENUM — model as varchar
createDomainno domains — a domain is a CHECK constraint, and RisingWave has no CHECK

Caveats / not-yet-verified#

Full-text search (MATCH-style predicates) is refused across the query
builder layer for RisingWave: the comment in
src/query-builders/functions/fulltext.ts notes it "was added with its
dialect and not verified against a server" and that RisingWave "has no
MATCH-style predicate at all," so the builder refuses rather than guessing.
Vector indexes are RisingWave's own technical preview (v2.6+) and only index
append-only inputs (an append-only table or materialized view).
WATERMARK ... WITH TTL is accepted on tables only; a source watermark with
withTtl: true throws.

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.
Capabilityrisingwave
Transactions atomicyes
Savepointsno — a nested transaction() throws
Isolationup to SERIALIZABLE
Transaction modesread-only yes; deferrable yes; constraint deferral yes
RETURNINGRETURNING on INSERT
Upsertrefused — RisingWave's INSERT has no ON CONFLICT clause — conflict handling is a property of the table (CREATE TABLE ... ON CONFLICT OVERWRITE
JSON columnJSONB (JSONB → JSONB)
Vector columnVECTOR(3)
Array columnINTEGER[]
WHERE builder62 operator keys; $and/$or/$not; $exists: yes; $in subquery: yes; expression operands: yes
SQL objectsfamily materialize: triggers no; procedures no; functions no; materialized views native; sequences no; enums check; RLS no
StreamingqueryStream() present; LISTEN present; createExtension() present

Related reading#

All dialects
PostgreSQL dialect — everything inherited (read path,
pooling, escaping, $n binding)
Materialize dialect — a sibling streaming/Postgres-wire
dialect with a very similar shape (sources, sinks, always-current
materialized views, refusal of most OLTP-only PostgreSQL)
CREATE TABLE
CREATE SOURCE
CREATE SINK
Subscription
Time windows
Emit on window close
Modified at 2026-10-04 00:40:16
Previous
Amazon Redshift Data API Dialect
Next
rqlite Dialect
Built with