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

Oracle Dialect

Oracle Database is an enterprise-grade relational database. prorm talks to it through
the oracledb driver. This guide covers how
to connect, the data-type mapping, sequences, Oracle's positional bind style, and the
Oracle-specific quirks you need to know about.
The implementation lives in oracle.
It targets Oracle 19c / 21c primarily (several 23c-only conveniences are emulated — see
Quirks). This dialect is functional but has gaps; the honest state of each
feature is called out below.

Overview#

Driver: oracledb (OracleDialect.library === 'oracledb')
Identifier quoting: double quotes ("MyTable"). Unquoted identifiers fold to
uppercase, so mixed-case names created through the ORM must always be referenced quoted.
Bind style: positional :1, :2, … (Oracle has no ? placeholder support).
Booleans: no native boolean — mapped to NUMBER(1).
Auto-increment: no AUTO_INCREMENT/SERIAL — use sequences.
Pooling: always on. connect() builds an oracledb connection pool.
PropertyValue
Dialect nameoracle
Extendsnothing — implements Dialect directly
Driveroracledb
Cloud SDKnone
Default port1521
Local runtimeprorm db up --dialect oracle (gvenzl/oracle-free:23.5-slim); docker-compose.test.yml

Quick start#

Install#

$ npm install ts-prorm-orm oracledb
$ pnpm add ts-prorm-orm oracledb
$ yarn add ts-prorm-orm oracledb
$ bun add ts-prorm-orm oracledb

Connect#

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

export const db = new Prorm({
  dialect: 'oracle',
  host: 'localhost',
  database: 'FREEPDB1', // the service name
  username: 'app',
  password: process.env.DB_PASSWORD,
});
import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'oracle',
  url: 'oracle://app:secret@localhost:1521/FREEPDB1',
});
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.

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' });
MERGE statement
upsert() also reads the row by primary key before and after the write, to return the instance.

Pagination#

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

Transaction with a savepoint#

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

Skip locked rows (SKIP LOCKED)#

A worker that claims rows from a queue table should pass over rows another transaction holds rather than wait for them. lock with skipLocked inside a transaction:
await db.transaction(async (t) => {
  await User.findAll({ where: { name: 'Ada' }, lock: { level: 'UPDATE', skipLocked: true }, transaction: t });
});
Type mapping for the portable descriptors: STRING → VARCHAR2(255), auto-increment INTEGER → NUMBER(10), BOOLEAN → NUMBER(1), DATE → DATE, UUID → RAW(16), JSON → CLOB. The type comparison lines the major engines up side by side.

Connection#

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

const prorm = new Prorm({
  dialect: 'oracle',
  host: 'localhost',
  port: 1521,      // default 1521
  database: 'ORCL', // the service name
  username: 'system',
  password: 'password',
});

await prorm.connect();
Under the hood the dialect assembles an Easy Connect string from your options:
// From OracleDialect.connect():
connectString: `${host}:${port}/${database}` // e.g. "localhost:1521/ORCL"
Honest note: there is no dedicated connectString or TNS-alias option. The connect
string is always built from host, port, and database. If you need a full descriptor
or a wallet-based connection, those are not currently wired through the dialect options.

Working directly with the dialect#

You can also instantiate the dialect on its own:
import { createOracleDialect } from 'ts-prorm-orm';

const oracle = createOracleDialect({
  host: 'localhost',
  port: 1521,
  database: 'ORCL',
  username: 'system',
  password: 'password',
  thinMode: true, // stay in pure-JS thin mode; skip Instant Client init
  pool: { max: 10, min: 2, increment: 2, timeout: 30 },
  schema: 'APP', // default schema for sequences/procedures/triggers
});

await oracle.connect();
const { rows } = await oracle.query('SELECT * FROM DUAL');
await oracle.disconnect();

Thin vs thick mode#

// thinMode: true  -> pure-JS driver, no Oracle Instant Client required.
// thinMode: false -> calls oracledb.initOracleClient() (thick mode, needs Instant Client).
By default (thinMode unset/false) the dialect calls oracledb.initOracleClient(), which
requires an Instant Client installation. Set thinMode: true to stay in the driver's
pure-JS mode.

Connection retry#

Connection-level errors can be retried automatically:
const oracle = createOracleDialect({
  /* ... */
  retry: {
    max: 3,
    timeout: 5000,
    backoff: true,
    backoffMultiplier: 2,
    backoffMax: 10000,
    match: ['ORA-12514', 'ORA-12541', 'ORA-12154', 'ECONNREFUSED'],
  },
});

Data types#

The ORM's abstract types map to Oracle as follows (see mapDataType()):
ORM typeOracle typeNotes
STRING(n)VARCHAR2(n)default n = 255
CHAR(n)CHAR(n)default n = 1
TEXT / MEDIUMTEXT / LONGTEXTCLOB
INTEGERNUMBER(10)length overridable
BIGINTNUMBER(19)
DECIMAL(p,s) / NUMERIC / NUMBERNUMBER(p,s)precision/scale honored
FLOAT / DOUBLEFLOAT
BOOLEANNUMBER(1)no native boolean — true/false escape to 1/0
DATEDATE
DATETIME / TIMESTAMPTIMESTAMP
DATEONLYDATE
TIMEVARCHAR2(8)stored as a string
BLOBBLOB
BINARY(n) / VARBINARY / RAWRAW(n)
JSONCLOBstored as text
JSONBBLOB
UUIDRAW(16)
GEOMETRYSDO_GEOMETRY
CLOB / NCLOB / BFILE / XMLTYPE / LONG_RAWnative equivalentsOracle-specific
Anything unrecognized falls back to VARCHAR2(255).
await oracle.createTable('EMPLOYEES', {
  ID:          { type: 'INTEGER', primaryKey: true },
  NAME:        { type: { key: 'STRING', length: 100 }, allowNull: false },
  SALARY:      { type: { key: 'DECIMAL', precision: 12, scale: 2 } },
  IS_ACTIVE:   { type: 'BOOLEAN', defaultValue: true },  // -> NUMBER(1) DEFAULT 1
  RESUME:      { type: 'BLOB' },
  BIO:         { type: 'TEXT' },                          // -> CLOB
  CREATED_AT:  { type: 'TIMESTAMP' },
});

Value escaping quirks#

Date values escape to TO_DATE('YYYY-MM-DD HH24:MI:SS', ...).
Buffer values escape via HEXTORAW('deadbeef') so raw bytes land in RAW/BLOB.
Booleans escape to '1' / '0' (consistent with the NUMBER(1) mapping).

Sequences#

Oracle has no auto-increment column; you generate surrogate keys with sequences.
await oracle.createSequence({
  name: 'EMPLOYEE_SEQ',
  startWith: 1000,
  incrementBy: 1,
  cache: 20,
  schema: 'APP',
});

// Fetch the next value (SELECT ... .NEXTVAL FROM DUAL)
const nextId = await oracle.nextSequenceValue('EMPLOYEE_SEQ');

// Existence check / listing
await oracle.hasSequence('EMPLOYEE_SEQ', 'APP');
const all = await oracle.listSequences(); // ["APP.EMPLOYEE_SEQ", ...]

// Drop (ifExists is emulated for pre-23c — see Quirks)
await oracle.dropSequence('EMPLOYEE_SEQ', { ifExists: true, schema: 'APP' });
Supported createSequence options: startWith, incrementBy, minvalue, maxvalue,
cycle, cache, nocache, order, replace, ifNotExists, schema.
Gap — no CURRVAL helper. Only nextSequenceValue() (NEXTVAL) is implemented.
There is no currSequenceValue() / CURRVAL method on the dialect. If you need the
current value, issue it yourself via query():
const { rows } = await oracle.query(
  'SELECT "EMPLOYEE_SEQ".CURRVAL AS "value" FROM DUAL',
);
(Remember CURRVAL is only valid in a session that has already called NEXTVAL.)
Note — default schema is SYSTEM. Sequence names are qualified with
options.schema → config.schema → 'SYSTEM'. Set a schema in the dialect options
or per call to avoid accidentally targeting SYSTEM.

Bind parameters (:n style)#

Oracle uses positional binds :1, :2, … — there is no ? placeholder. The query
builders emit this style, and query() accepts a positional array (or a named object for
:name binds):
// Named binds
await oracle.query(
  'SELECT * FROM "EMPLOYEES" WHERE "DEPT_ID" = :dept',
  { replacements: { dept: 10 } },
);

// Positional binds
await oracle.query(
  'SELECT * FROM "EMPLOYEES" WHERE "SALARY" > :1 AND "DEPT_ID" = :2',
  { replacements: [50000, 10] },
);
buildInsertQuery / buildUpdateQuery generate :n placeholders:
const { sql, values } = oracle.buildInsertQuery('EMPLOYEES', {
  ID: 1001, NAME: 'Ada', SALARY: 90000,
});
// INSERT INTO "EMPLOYEES" ("ID", "NAME", "SALARY") VALUES (:1, :2, :3)

RETURNING ... INTO#

Because Oracle has no ? binds, RETURNING uses OUT binds that continue the :n
numbering after the insert's own binds:
const { sql } = oracle.buildInsertQuery(
  'EMPLOYEES',
  { NAME: 'Ada', SALARY: 90000 },
  { returning: ['ID'] },
);
// INSERT INTO "EMPLOYEES" ("NAME", "SALARY") VALUES (:1, :2) RETURNING "ID" INTO :3
Passing returning: true returns the ROWID instead.
Caveat — mixed placeholder styles. The WHERE-clause builder emits ? markers while
INSERT/UPDATE SET clauses emit :n. For raw statements prefer building your own SQL
with explicit :n binds (or interpolate through replaceReplacements()), rather than
relying on ? reaching the driver.

Pagination#

buildSelectQuery paginates by wrapping the query and filtering on ROWNUM:
const { sql } = oracle.buildSelectQuery({
  tableName: 'EMPLOYEES',
  order: { SALARY: 'DESC' },
  limit: 10,
  offset: 20,
});
// SELECT * FROM ( ... ) WHERE ROWNUM > 20 AND ROWNUM <= 30
Gap — buildLimitOffset(). The standalone buildLimitOffset() helper emits only a
bare WHERE ROWNUM <= n and does not skip the first offset rows. Prefer
buildSelectQuery (which wraps correctly), or use queryStream() for streaming, which
routes through a correct ROWNUM-windowed helper.

Upsert (MERGE)#

buildUpsertQuery compiles to a MERGE INTO ... USING (SELECT ... FROM DUAL) statement and
supports composite conflict keys:
const { sql } = oracle.buildUpsertQuery(
  'EMPLOYEES',
  { ID: 1001, NAME: 'Ada', SALARY: 90000 },
  { conflictFields: ['ID'] },
);
// MERGE INTO "EMPLOYEES" USING (SELECT :1 AS "ID", :2 AS "NAME", :3 AS "SALARY" FROM DUAL) "src"
//   ON ("EMPLOYEES"."ID" = "src"."ID")
//   WHEN MATCHED THEN UPDATE SET ...
//   WHEN NOT MATCHED THEN INSERT (...) VALUES (...)
A general-purpose buildMergeQuery() is also available for hand-written merges (composite
on keys, conditional WHEN MATCHED, WHEN MATCHED ... THEN DELETE, etc.).

Oracle-specific query builders#

These are implemented and Oracle-idiomatic:
buildWindowFunction() — analytic functions, e.g.
ROW_NUMBER() OVER (PARTITION BY "dept" ORDER BY "salary" DESC).
buildCTE() — WITH ... AS (...). Recursive simply by supplying unionQuery
(Oracle has no RECURSIVE keyword).
buildConnectByQuery() — hierarchical START WITH ... CONNECT BY PRIOR queries with
optional NOCYCLE, ORDER SIBLINGS BY, and LEVEL/CONNECT_BY_ISLEAF pseudo-columns.

Transactions#

const tx = await oracle.startTransaction({ isolationLevel: 'SERIALIZABLE' });
// ... do work ...
await oracle.commitTransaction(tx);   // commits + closes the tx connection
// or: await oracle.rollbackTransaction(tx);
Only READ COMMITTED and SERIALIZABLE (plus READ ONLY) are accepted; the ANSI
READ UNCOMMITTED / REPEATABLE READ levels throw a DatabaseError (Oracle doesn't have
them). Savepoint SQL helpers (createSavepointSQL, releaseSavepointSQL,
rollbackToSavepointSQL) are provided.
Important gap — query() does not join an open transaction. startTransaction()
holds its own pooled connection, but query() acquires a separate connection from the
pool and runs with autoCommit: true. Statements executed through query() are therefore
not part of a transaction started with startTransaction(). To run statements
transactionally, execute them on tx's own connection directly.

Quirks#

IF [NOT] EXISTS is emulated for 19c/21c#

Native IF [NOT] EXISTS on CREATE/DROP is 23c-only and raises ORA-00922 on older
releases. For tables, schemas (users), and sequences, the dialect instead runs the plain
DDL wrapped in a PL/SQL block that swallows the specific "already exists" / "does not exist"
ORA- code (e.g. ORA-00955, ORA-00942, ORA-01918, ORA-02289). So ifExists /
ifNotExists work portably.

A schema is a user#

Oracle has no standalone schema object — a schema is a user. createSchema() therefore
runs CREATE USER with a randomly generated password; if you need a specific password,
create the user through the user-management API instead. dropSchema() runs
DROP USER ... CASCADE.

queryStream()#

Streaming uses a dedicated ROWNUM-windowed helper (createOracleQueryStream) rather than
the buggy buildLimitOffset(), so paginated streams skip offsets correctly.

Partitioning#

createPartitionedTable() supports RANGE, LIST, HASH, INTERVAL, and REFERENCE
partitioning, plus subpartitions. Since Oracle has no PostgreSQL-style ATTACH/DETACH PARTITION, attachPartition() / detachPartition() are implemented via
ALTER TABLE ... EXCHANGE PARTITION ... WITH TABLE .... listPartitions(),
modifyPartition(), and addPartition() are available.

Materialized views#

createMaterializedView() supports BUILD IMMEDIATE/DEFERRED, REFRESH FAST/COMPLETE/FORCE,
and ON COMMIT/DEMAND. Oracle has no OR REPLACE/IF NOT EXISTS for MVs, so replace
drops-then-recreates. refreshMaterializedView() calls DBMS_MVIEW.REFRESH (there is no
REFRESH MATERIALIZED VIEW statement in Oracle); PostgreSQL's CONCURRENTLY is ignored and
treated as FORCE.

Unsupported features (these throw)#

The following are intentionally not implemented and throw an explanatory error:
Foreign Data Wrappers (createForeignDataWrapper, createForeignServer,
createForeignTable, user mappings, …) — Postgres-specific; use CREATE DATABASE LINK.
Extensions (createExtension, dropExtension, …) — Postgres-specific.
changeOwner — not supported in Oracle.
addConstraint / removeConstraint — throw. Use createConstraint() /
dropConstraint() (which are implemented) instead.
createSecurityPolicy / dropSecurityPolicy — throw ("Security policies are not
supported"). (Oracle VPD is not wired through these methods.)

See also#

Source: oracle
Driver: node-oracledb

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.
Capabilityoracle
Transactions atomicyes
Savepointsyes (no explicit RELEASE)
Isolationup to SERIALIZABLE (accepted: READ COMMITTED, SERIALIZABLE); native levels READ ONLY
Transaction modesread-only no; deferrable no; constraint deferral no
RETURNINGRETURNING on INSERT
UpsertMERGE INTO … WHEN MATCHED / WHEN NOT MATCHED
JSON columnCLOB (JSONB → BLOB)
Vector columnVECTOR(3, FLOAT32)
Array columnVARCHAR2(255)
WHERE builder34 operator keys; $and/$or/$not; $exists: no; $in subquery: no; expression operands: no
SQL objectsfamily oracle: triggers yes; procedures yes; functions multiStatement; materialized views native; sequences yes; enums check; RLS no
StreamingqueryStream() present; LISTEN absent; createExtension() present

Testing#

tests/dialects/oracle.test.ts exercises the dialect with a mocked driver, so nothing touches a server. A live instance: prorm db up --dialect oracle (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
openGauss Dialect
Next
Oracle Autonomous Database Dialect
Built with