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

openGauss Dialect

Overview#

openGauss is Huawei's open-source relational database,
forked from PostgreSQL 9.2.4. It speaks the PostgreSQL frontend/backend wire
protocol, so OpenGaussDialect extends PostgresDialect and reuses the
pg driver
— connection pooling, $n parameter binding, escaping, and the
bulk of the query builders are inherited unchanged.
PropertyValue
Dialect nameopengauss
ExtendsPostgresDialect (postgres)
Driverpg
Cloud SDKnone
Default port5432
Local runtimeself-hosted; no image in this repo
The fork point is what makes this dialect more than a rename. Everything
PostgreSQL gained after 9.2 exists in openGauss only if openGauss chose to
backport it, and where it did not — or where it backported a different
spelling — an inherited-verbatim Postgres dialect emits SQL that an openGauss
server refuses. This is the largest set of real divergences of any
compatibility-family dialect in this library.
Key facts (from src/dialects/opengauss/index.ts):
Dialect name is 'opengauss'. The underlying driver library stays pg.
Default port is 5432, the same as PostgreSQL. No override is needed.
Authentication is the thing most likely to stop you. See the next section
before anything else.

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: 'opengauss',
  host: 'localhost',
  database: 'postgres',
  username: 'app',
  password: process.env.DB_PASSWORD,
});
import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'opengauss',
  url: 'opengauss://app:secret@localhost:5432/postgres',
});
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) },
  meta: { type: DataTypes.JSONB() },
});

await db.sync(); // CREATE TABLE — see Generated SQL below
meta is JSONB, which the containment query below needs.

Query#

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

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

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

Generated SQL#

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

Create table#

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

Insert, update and delete#

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

Upsert#

await User.upsert({ id: 1, email: 'ada@example.com', name: 'Ada Lovelace' });
upsert() also reads the row by primary key before and after the write, to return the instance.

Pagination#

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

JSON#

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

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

Transaction with a savepoint#

await db.transaction(async (t) => {
  await User.create({ email: 'grace@example.com', name: 'Grace' }, { transaction: t });
  // A nested transaction is a SAVEPOINT; its failure undoes only its own work.
  await db
    .transaction(async (sp) => {
      await User.destroy({ where: { id: 1 }, transaction: sp });
      throw new Error('keep the row');
    }, { transaction: t })
    .catch(() => {});
});

Table sampling#

sample on the select builder reads a random fraction of the table, for estimates over large tables:
const sample = db.getDialectInstance()!.buildSelectQuery({
  tableName: 'users',
  sample: { method: 'BERNOULLI', percent: 10 },
});
await db.query(sample.sql);
Type mapping for the portable descriptors: STRING → VARCHAR(255), auto-increment INTEGER → SERIAL, BOOLEAN → BOOLEAN, DATE → TIMESTAMP, UUID → UUID, JSON → JSON. The type comparison lines the major engines up side by side.

Connection#

⚠️ The pg driver cannot authenticate against a stock openGauss install#

openGauss defaults password_encryption_type to sha256, an
openGauss-proprietary authentication method that neither libpq nor the pure-JS
pg driver implements. A connection through this dialect will fail to
authenticate against a default install, and the error will be about the
authentication method rather than about anything you did.
To use the pg driver you must switch the server to md5:
1.
ALTER SYSTEM SET password_encryption_type = 0; (or set it in
postgresql.conf) and restart.
2.
Add an md5 line for your host to pg_hba.conf.
3.
Re-set the user's password — the existing one is still stored as a
sha256 hash and will not be re-derived.
The alternative is a driver that implements the sha256 handshake — the
official openGauss-connector-nodejs, or the pg-opengauss fork. This
dialect does not bundle either; it uses pg.
This is a deployment prerequisite, not something the dialect can work around.
import { Prorm } from 'ts-prorm-orm';

const db = new Prorm({
  dialect: 'opengauss',
  host: '127.0.0.1',
  port: 5432,
  username: 'app',
  password: '...',
  database: 'postgres',
});

What differs from Postgres#

OpenGaussDialect extends PostgresDialect (postgres) and
overrides 22 of its methods (Object.getOwnPropertyNames(OpenGaussDialect.prototype),
computed by the scratch test); everything else is inherited unchanged.
AreaOverridden
Connection and executionlisten, notify, startTransaction, unlisten
DML buildersbuildInsertQuery, buildUpsertQuery, formatDefaultValue
TypesbuildColumnDefinitionSql
DDL and schemaaddIndex, attachPartition, buildAddPartitionSQL, buildCreatePartitionedTableSQL, buildPartitionSql, createIndex, createPartition, createPartitionedTable, detachPartition
IntrospectionassertIndexMethod
OtherbuildDuplicateKeyUpdateClause, buildStorageClause, quoteBound, toOpenGaussPartition

Divergences from PostgreSQL#

Upsert — openGauss has no ON CONFLICT#

ON CONFLICT arrived in PostgreSQL 9.5, after the fork, and openGauss never
took it. A real server answers:
syntax error at or near "CONFLICT"
What openGauss has instead is the MySQL-shaped INSERT ... ON DUPLICATE KEY UPDATE, which names no conflict target — the server infers it from the table's
unique constraints. buildInsertQuery (with options.upsert) and
buildUpsertQuery emit that form:
db.dialect.buildUpsertQuery('kv', { k: 'a', v: 1 });
Two consequences worth calling out:
conflictFields is not required. The Postgres base throws without it,
because ON CONFLICT cannot infer its target. openGauss's grammar has nowhere
to put a conflict target at all, so one passed for cross-dialect portability
is accepted and ignored.
VALUES(col), not excluded.col. VALUES(col) is the spelling openGauss
documents for reaching the row that would have been inserted.
updateOnDuplicate restricts the update set as elsewhere:
db.dialect.buildUpsertQuery('users', { id: 1, name: 'Ada', email: 'a@x.io' }, {
  updateOnDuplicate: ['name'],
});
// ... ON DUPLICATE KEY UPDATE "name" = VALUES("name")

RETURNING after an upsert#

openGauss supports INSERT ... RETURNING for a plain insert — that path is
inherited from the Postgres dialect and works — but not in combination with
ON DUPLICATE KEY UPDATE. Requesting both throws:
openGauss does not support RETURNING together with ON DUPLICATE KEY UPDATE
(its only upsert form). Re-fetch the row after the upsert instead.

LISTEN / NOTIFY are not implemented#

openGauss answers LISTEN statement is not yet supported. The Postgres dialect
exposes listen() / unlisten() / notify() and holds a dedicated pg client
for the subscription — so inheriting it would open and keep a connection for a
channel that can never fire. All three throw here instead. Use polling or an
external message queue for change notification.

Partitioning is Oracle-shaped, not PostgreSQL 10 declarative#

openGauss did not adopt PostgreSQL 10's declarative partitioning. Every
partition is declared inline in CREATE TABLE, and a range bound is an
exclusive VALUES LESS THAN (...) rather than FOR VALUES FROM (...) TO (...).
Neither statement parses on the other engine.
db.dialect.buildCreatePartitionedTableSQL(
  'events',
  { id: { type: 'INTEGER' }, ts: { type: 'TIMESTAMP' } },
  {
    type: 'range',
    column: 'ts',
    partitions: [
      { name: 'p2024', lessThan: '2025-01-01' },
      { name: 'pmax', lessThan: 'MAXVALUE' },
    ],
  },
);
List partitions carry a bare value set (VALUES ('de', 'fr'), or
VALUES (DEFAULT) for the catch-all); hash partitions carry only names, since
openGauss derives the buckets from the partition count.
Because there is no CREATE TABLE ... PARTITION OF, a range or list partitioned
table must declare its partitions up front — asking for one with an empty
partition list throws rather than emitting a table that cannot be created.
createPartitionedTable() accepts the same { partitionBy, partitions } option
shape as the Postgres base, translating a shared PartitionDefinition's to
bound into VALUES LESS THAN. A range partition's from has no openGauss
counterpart: partitions are contiguous, and each one's lower bound is the
previous one's upper bound.
Later partitions are added with ALTER TABLE ... ADD PARTITION, and only at the
end of the range:
db.dialect.buildAddPartitionSQL({ parentTable: 'events', name: 'p2026', bound: { from: 0, to: 100 } });
attachPartition() and detachPartition() throw. openGauss has neither
ATTACH PARTITION nor DETACH PARTITION; the nearest operations are
ADD PARTITION for a genuinely new partition and EXCHANGE PARTITION to swap
in an identically-shaped table. Neither preserves a detached partition as a
standalone table the way DETACH does, so they are not silently remapped.

Index methods — no BRIN, no SP-GiST#

openGauss offers:
MethodWhere it applies
btreeRow-store (Astore), the default
ubtreeRow-store (Ustore engine)
hashRow-store
ginRow-store and column-store
gistRow-store
psortColumn-store, the default there
PostgreSQL's brin and spgist are not available. Passing either to
addIndex() or createIndex() throws up front, naming the dialect, rather than
reaching the server as CREATE INDEX ... USING brin (...) and failing with an
access-method error that mentions nobody.

Column-store tables#

WITH (ORIENTATION = COLUMN) creates a column-oriented (analytics) table — an
openGauss storage option with no PostgreSQL equivalent.
db.dialect.buildStorageClause({ orientation: 'COLUMN', compression: 'HIGH' });
// " WITH (ORIENTATION = COLUMN, COMPRESSION = HIGH)"
A table that requests neither produces an empty clause, so ordinary row-store
DDL stays byte-identical to what the Postgres dialect emits.

Accepted, but not what it says#

These emit valid SQL and are therefore not rejected — but the semantics differ,
so relying on the PostgreSQL meaning is a bug.

SERIALIZABLE is really REPEATABLE READ#

openGauss accepts the keyword and runs the transaction at REPEATABLE READ. There
is no serializable-snapshot isolation, so there is no protection against write
skew
. startTransaction() warns rather than throwing, because the statement
does execute — failing the transaction outright would be worse than saying so:
openGauss maps SERIALIZABLE to REPEATABLE READ: it has no serializable-snapshot
isolation, so this transaction is not protected against write skew.

Other inherited-but-different behaviour#

SERIAL on a temporary table is rejected by openGauss
(It's not supported to create serial column on temporary table). SERIAL
on an ordinary table works exactly as in PostgreSQL.
Binary COPY differs subtly from PostgreSQL's and can fail with
unexpected EOF against PostgreSQL-native binary COPY tooling. Text-format
COPY is unaffected.
nextval() runs only on the primary node, never on a standby — relevant
if you route reads to a standby in an HA topology.

Inherited PostgreSQL behavior#

Everything not listed above is inherited from PostgresDialect and behaves as
documented for the PostgreSQL dialect — double-quoted
identifiers, $n placeholders, SELECT/UPDATE/DELETE builders, JSON/JSONB
helpers, LIMIT/OFFSET, FOR UPDATE locking, and the type mapping.
openGauss does support, and so these are left alone: jsonb, uuid, arrays,
interval, range types, TABLESAMPLE, CREATE INDEX CONCURRENTLY (but not on
column-store, temporary or partitioned tables, and not inside a transaction
block), event triggers, CREATE PROCEDURE, anonymous DO blocks, and
NOWAIT row locking.

Caveats / not-yet-verified#

SQL generation is verified; live execution is not. Every SQL snippet on
this page is the exact output of a builder asserted in
tests/dialects/opengauss.test.ts, which runs without any database
connection
. None of it has been executed against a live openGauss server in
this repository — and given the sha256 authentication prerequisite above, a
connection is a deployment exercise in its own right.
SKIP LOCKED is unconfirmed. NOWAIT is documented; SKIP LOCKED was
not found in openGauss's locking documentation either way. The inherited lock
builder will emit it if asked. Verify before relying on it.
Several PostgreSQL features could not be confirmed either way because the
official documentation pages did not render fetchable body text: the FILTER
aggregate clause, GROUPING SETS/CUBE/ROLLUP, LATERAL joins, INCLUDE
covering indexes, pg_trgm, and TRUNCATE ... RESTART IDENTITY. All are
emitted by inherited builders and none is rejected here. Test them against
your server rather than assuming the PostgreSQL answer.
Reserved words have not been diffed. No openGauss-vs-PostgreSQL keyword
diff was available. All identifiers are double-quoted by the inherited
escaping, which covers the common case; run
SELECT * FROM pg_get_keywords() against both engines if you need precision.
Introspection helpers inherited from Postgres query pg_catalog /
information_schema and have not been checked against openGauss's catalogs.
GENERATED ALWAYS AS IDENTITY and stored generated columns are reported as
supported but were not confirmed from primary documentation.

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.
Capabilityopengauss
Transactions atomicyes
Savepointsyes
Isolationup to SERIALIZABLE
Transaction modesread-only yes; deferrable yes; constraint deferral yes
RETURNINGRETURNING on INSERT
UpsertINSERT … ON DUPLICATE KEY UPDATE
JSON columnJSON (JSONB → JSONB)
Vector columnVECTOR(3)
Array columnINTEGER[]
WHERE builder62 operator keys; $and/$or/$not; $exists: yes; $in subquery: yes; expression operands: yes
SQL objectsfamily unknown: triggers no; procedures no; functions no; materialized views no; sequences no; enums check; RLS no
StreamingqueryStream() present; LISTEN present; createExtension() present

Related reading#

All dialects — what each engine supports
PostgreSQL dialect — everything inherited unchanged
Data types — how each type maps to this engine
Querying — how a FindOptions becomes SQL
Modified at 2026-10-04 00:40:16
Previous
OceanBase Dialect
Next
Oracle Dialect
Built with