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

SAP HANA Dialect

The hana dialect targets SAP HANA — both on-premise HANA 2.0 and the
continuously-delivered HANA Cloud editions. It is implemented in
hana on top of
SAP's official hdb client: a pure
JavaScript, callback-based driver with no native bindings.
HANA is a column-store-first, in-memory HTAP database. The dialect leans into
that: tables are column tables by default, and HANA-native constructs like
UPSERT ... WITH PRIMARY KEY, GENERATED ALWAYS AS IDENTITY, sequences, and
system-versioned temporal tables are all first-class.

Overview#

Dialect key'hana'
Driver / libraryhdb
Default port30015
Default userSYSTEM
Identifier quotingDouble quotes ("col"), case-sensitive
Default table storageColumn store (CREATE COLUMN TABLE)
PaginationLIMIT n OFFSET m
UpsertNative UPSERT ... WITH PRIMARY KEY
PropertyValue
Dialect namehana
Extendsnothing — implements Dialect directly
Driverhdb
Cloud SDKnone
Default port30015
Local runtimeself-hosted; no image in this repo
Install the driver alongside the ORM:
The hdb package ships no bundled TypeScript types; the dialect provides its
own minimal ambient shim (src/dialects/hana/hdb.d.ts), so you do not need
@types/hdb.

Quick start#

Install#

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

Connect#

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

export const db = new Prorm({
  dialect: 'hana',
  host: 'my-instance.hanacloud.ondemand.com',
  port: 443,
  username: 'DBADMIN',
  password: process.env.DB_PASSWORD,
  dialectOptions: {
    schema: 'APP',
    useTLS: true, // required by HANA Cloud
  },
});

Define a model#

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

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

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

Query#

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

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

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

Generated SQL#

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

Create table#

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

Insert, update and delete#

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

Upsert#

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

await db.transaction(async (t) => {
  await User.create({ email: 'grace@example.com', name: 'Grace' }, { transaction: t });
  await User.update({ name: 'Grace Hopper' }, { where: { email: 'grace@example.com' }, transaction: t });
});
[!WARNING] No savepoints
Nested transactions need savepoints, and hana has none. Run the work in a single transaction, or restructure it so nothing nests.

Fail fast on a locked row (NOWAIT)#

lock with nowait makes the statement fail at once instead of waiting for another transaction's lock:
await db.transaction(async (t) => {
  await User.findAll({ where: { id: 1 }, lock: { level: 'UPDATE', nowait: true }, transaction: t });
});
Type mapping for the portable descriptors: STRING → NVARCHAR(255), auto-increment INTEGER → INTEGER, BOOLEAN → BOOLEAN, DATE → TIMESTAMP, UUID → NVARCHAR(36), JSON → NCLOB. The type comparison lines the major engines up side by side.

Connection#

Connect through the Prorm constructor with dialect: 'hana'. HANA-specific
options (schema, useTLS, extraOptions) are passed under dialectOptions.
import { Prorm } from 'ts-prorm-orm';

const prorm = new Prorm({
  dialect: 'hana',
  host: 'my-hana-host.hanacloud.ondemand.com',
  port: 30015,
  username: 'DBADMIN',
  password: 'secret',
  database: 'HXE', // tenant database name (optional)
  dialectOptions: {
    schema: 'MY_APP',   // default schema for unqualified references
    useTLS: true,       // required for HANA Cloud
    // Any additional raw hdb.createClient() options:
    extraOptions: { encrypt: true, sslValidateCertificate: false },
  },
});

await prorm.connect();
Defaults if omitted: host: 'localhost', port: 30015, username: 'SYSTEM',
password: ''.
The default port 30015 follows SAP's 3<instance>15 convention — the SQL
port of the tenant database's index server on a Multi-Database Container (MDC)
system using instance number 00 (30013 is the system database on the same
instance; instance 01 uses 30115/30117).

HANA Cloud vs on-premise#

HANA Cloud connections require TLS (useTLS: true). You can detect which
edition you are connected to — the dialect parses SYS.M_DATABASE.VERSION
(HANA Cloud reports a 4.x-prefixed version; on-premise HANA 2.0 reports
2.x). Reach the live dialect instance with getDialectInstance(). The
edition helpers are HANA-specific (not on the shared Dialect interface), so
cast to reach them:
const dialect = prorm.getDialectInstance()!;

const hana = dialect as unknown as {
  getEditionInfo(): Promise<{
    edition: 'cloud' | 'on-premise' | 'unknown';
    version: string;
    major?: number;
    minor?: number;
    revision?: number;
  }>;
  isCloudEdition(): Promise<boolean>;
};

const info = await hana.getEditionInfo();

if (await hana.isCloudEdition()) {
  // branch on Cloud-only feature availability
}
The remaining examples in this guide operate on that same dialect instance
returned by getDialectInstance().

Column vs row tables#

HANA's signature feature is the column store. Tables are created as
CREATE COLUMN TABLE by default. To create a legacy row-store table, pass
the HANA-specific columnStore: false flag through TableOptions:
// Column table (default) — best for analytics and most workloads
await dialect.createTable('events', {
  id: { type: 'BIGINT', autoIncrement: true, primaryKey: true },
  payload: { type: 'JSON' },
  created_at: { type: 'TIMESTAMP' },
});
// -> CREATE COLUMN TABLE "events" (...)

// Row table — for narrow, high-frequency single-row OLTP access patterns
await dialect.createTable(
  'sessions',
  {
    token: { type: 'NVARCHAR', length: 64, primaryKey: true },
    user_id: { type: 'BIGINT' },
  },
  { columnStore: false },
);
// -> CREATE ROW TABLE "sessions" (...)
Auto-increment columns emit GENERATED ALWAYS AS IDENTITY (START WITH 1 INCREMENT BY 1) rather than a serial/AUTO_INCREMENT keyword.

System-versioned (temporal) tables#

Column tables can opt into HANA's system-versioning for automatic history
tracking. The dialect appends the valid_from/valid_to period columns and a
PERIOD FOR SYSTEM_TIME clause:
await dialect.createTable(
  'accounts',
  {
    id: { type: 'BIGINT', primaryKey: true },
    balance: { type: 'DECIMAL', precision: 15, scale: 2 },
  },
  { systemVersioning: { historyTable: 'accounts_history' } },
);
// -> CREATE COLUMN TABLE "accounts" (..., "valid_from" TIMESTAMP(6) NOT NULL
//    GENERATED ALWAYS AS ROW START, "valid_to" TIMESTAMP(6) NOT NULL GENERATED
//    ALWAYS AS ROW END, PERIOD FOR SYSTEM_TIME ("valid_from", "valid_to"))
//    WITH SYSTEM VERSIONING HISTORY TABLE "accounts_history"
If historyTable is omitted, HANA auto-generates and manages the history table.
System-versioning is column-store only — combining it with columnStore: false
throws. To retrofit an existing table, use alterTableSystemVersioning(), which
issues the required period-column and versioning ALTER TABLE statements in
order (HANA has no single-statement form for this).

Data types#

The dialect maps the ORM's generic type keys onto HANA-native types. HANA is a
Unicode-first engine, so string types map to their N-prefixed variants:
ORM typeHANA type
STRING / NVARCHARNVARCHAR(n) (length: 'max' → NCLOB)
CHARNCHAR(n)
TEXT / MEDIUMTEXT / LONGTEXTNCLOB
SHORTTEXTSHORTTEXT(n)
ALPHANUMALPHANUM(n)
INTEGERTINYINT / SMALLINT / INTEGER / BIGINT (by length 1/2/-/8)
TINYINT / BIGINTTINYINT / BIGINT
FLOATREAL
DOUBLEDOUBLE
DECIMAL / NUMERIC / NUMBERDECIMAL(p, s)
BOOLEAN / BITBOOLEAN
DATE / DATETIME / TIMESTAMPTIMESTAMP
SECONDDATESECONDDATE (second-precision timestamp)
DATEONLYDATE
TIMETIME
BLOBBLOB
BINARY / VARBINARYVARBINARY(n)
JSONNCLOB
JSONBBLOB
UUIDNVARCHAR(36)
ENUMNVARCHAR(255) (HANA has no native ENUM)
GEOMETRYST_GEOMETRY (optionally ST_GEOMETRY(srid))
ST_POINTST_POINT (optionally ST_POINT(srid))
Any unrecognized type string is passed through verbatim, so you can supply
HANA-native types directly (e.g. 'SECONDDATE', 'ALPHANUM(10)').

Pagination and LIMIT#

HANA uses the standard LIMIT n OFFSET m clause — unlike Oracle/Db2's
OFFSET ... FETCH FIRST .... There is one quirk: HANA does not allow a bare
OFFSET without a LIMIT.
When only an offset is supplied, the dialect emits
a sentinel maximum limit (2147483647) to satisfy the parser:
const { sql } = dialect.buildSelectQuery({
  tableName: 'events',
  offset: 100, // no limit given
});
// -> ... LIMIT 2147483647 OFFSET 100

Upserts#

The dialect prefers HANA's native UPSERT ... WITH PRIMARY KEY statement — a
genuine HANA-only construct distinct from the MERGE INTO every other
enterprise dialect uses. With no explicit conflict target, it matches on the
table's primary key:
const { sql, values } = dialect.buildUpsertQuery('accounts', {
  id: 42,
  balance: 100.5,
});
// -> UPSERT "accounts" ("id", "balance") VALUES (?, ?) WITH PRIMARY KEY
When you name explicit conflictFields other than the primary key, the dialect
falls back to a full MERGE INTO ... WHEN MATCHED / WHEN NOT MATCHED statement
(sourced from the single-row DUMMY pseudo-table), since UPSERT ... WITH PRIMARY KEY can only match on the actual primary key:
const { sql } = dialect.buildUpsertQuery(
  'accounts',
  { email: 'a@b.com', balance: 0 },
  { conflictFields: ['email'], updateOnDuplicate: ['balance'] },
);
// -> MERGE INTO "accounts" AS target USING (SELECT ? AS "email", ? AS "balance"
//    FROM DUMMY) AS source ON target."email" = source."email"
//    WHEN MATCHED THEN UPDATE SET "balance" = source."balance"
//    WHEN NOT MATCHED THEN INSERT (...) VALUES (...)

Sequences#

HANA has Oracle-style sequences accessed via NEXTVAL/CURRVAL pseudo-columns,
selected from the single-row DUMMY table (HANA's equivalent of Oracle's
DUAL):
await dialect.createSequence({ name: 'order_seq', startWith: 1000, incrementBy: 1 });

const next = await dialect.nextSequenceValue('order_seq'); // SELECT "order_seq".NEXTVAL FROM DUMMY
nextSequenceValue() is part of the shared Dialect interface. The HANA
dialect additionally exposes currSequenceValue() (emitting SELECT "order_seq".CURRVAL FROM DUMMY); reach it by casting the instance, since it is
a HANA-specific extra rather than a shared interface method.

Transactions#

hdb has no built-in connection pool, so each transaction is backed by its own
dedicated client connection (with autocommit disabled). This keeps a
transaction's statements from interleaving with unrelated queries on the shared
connection:
const tx = await dialect.startTransaction({ isolationLevel: 'SERIALIZABLE' });
try {
  await dialect.query('UPDATE "accounts" SET "balance" = "balance" - ? WHERE "id" = ?', {
    replacements: [50, 1],
    transaction: tx,
  });
  await dialect.commitTransaction(tx);
} catch (err) {
  await dialect.rollbackTransaction(tx);
  throw err;
}
The isolation level is applied via SET TRANSACTION ISOLATION LEVEL ... on the
dedicated connection before any statements run.

Identifiers and case folding#

This is the single biggest gotcha for developers coming from MySQL/Postgres.
HANA follows the Oracle/Db2 rule: unquoted identifiers are folded to
uppercase
. The dialect always quotes identifiers with double quotes, so an
identifier is stored and referenced exactly as written:
dialect.escapeId('users');   // -> "users"  (stays lowercase)
dialect.quoteTable('users', 'MY_APP'); // -> "MY_APP"."users"
Because of this, catalog lookups (describeTable, showTables, dropTable
with ifExists, etc.) uppercase the name when querying SYS.* views and scope
results to the configured schema (or CURRENT_SCHEMA) — without that scoping,
same-named tables across schemas would collide.

Quirks and limitations#

The dialect is honest about features HANA models differently or not at all —
these methods throw a descriptive error rather than emitting invalid SQL:
No materialized views. HANA has no CREATE MATERIALIZED VIEW. The nearest
equivalents are Calculation Views (modeled objects, out of scope for a CRUD
ORM) or a manually-refreshed snapshot table. createMaterializedView() and
friends throw.
No CREATE EXTENSION. Extensions are PostgreSQL-specific; the extension
methods throw.
Federation is Smart Data Access, not FDW. HANA's analogue of Postgres
foreign data wrappers is CREATE REMOTE SOURCE / CREATE VIRTUAL TABLE. It
does not map cleanly onto the generic (Postgres-shaped) FDW interface, so the
FDW methods throw with a pointer to Smart Data Access.
No partial (filtered) indexes. createPartialIndex() throws — HANA does
not support a WHERE clause on CREATE INDEX. Full-text (CREATE FULLTEXT INDEX), spatial (CREATE SPATIAL INDEX), and expression indexes are
supported.
No row-level-security policies. HANA uses Structured/Analytic Privileges
instead; createPolicy(), enableRLS(), etc. throw.
No ALTER ... OWNER TO. Object ownership is managed via privileges/roles,
so changeOwner() throws.
Partitioning: range and hash partitioning are modeled by
createPartitionedTable(). HANA's ROUNDROBIN partitioning is not modeled —
use raw SQL via query(). Attaching/detaching a standalone table as a
partition is not supported (attachPartition/detachPartition throw); use
ADD PARTITION / MERGE PARTITIONS instead.
Also worth noting:
ALTER TABLE column DDL is parenthesized and can batch multiple columns
in one clause (ADD (...), DROP (...), ALTER (...)), distinct from the
single-column-at-a-time syntax of most dialects. Column renames use a
dedicated RENAME COLUMN t.old TO new statement.
Stored procedures use SQLScript (LANGUAGE SQLSCRIPT). Calling a
procedure returns OUT/INOUT parameters plus zero or more result sets; the
dialect normalizes CALL results into { rows, rowCount, outputParams, resultSets }.
Recursive CTEs and window/OLAP functions are fully supported via
buildRecursiveCteClause() and buildWindowFunction() (e.g. ROW_NUMBER() OVER (PARTITION BY ... ORDER BY ...)).

See also#

Source: hana
Driver: hdb on npm
SAP HANA SQL Reference

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.
Capabilityhana
Transactions atomicyes
Savepointsno — a nested transaction() throws
Isolationup to SERIALIZABLE
Transaction modesread-only no; deferrable no; constraint deferral no
RETURNINGrefused — HANA does not support a RETURNING clause on INSERT. Re-fetch the row after the insert instead.
UpsertMERGE INTO … WHEN MATCHED / WHEN NOT MATCHED
JSON columnNCLOB (JSONB → BLOB)
Vector columnREAL_VECTOR(3)
Array columnrefused — SAP HANA has no ARRAY column type. Store the value as JSON, or model it as a child table.
WHERE builder32 operator keys; $and/$or/$not; $exists: yes; $in subquery: yes; expression operands: yes
SQL objectsfamily unknown: triggers no; procedures no; functions no; materialized views no; sequences no; enums check; RLS no
StreamingqueryStream() present; LISTEN absent; createExtension() present

Testing#

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

Related reading#

All dialects — what each engine supports
Data types — how each type maps to this engine
Querying — how a FindOptions becomes SQL
Modified at 2026-10-04 00:40:16
Previous
Greenplum Dialect
Next
MySQL HeatWave Dialect
Built with