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

Turso / libSQL Dialect

Overview#

Turso is a hosted database service built on
libSQL, an open-source fork of
SQLite. libSQL keeps SQLite's storage format and SQL grammar but adds the one
thing SQLite lacks natively: a network protocol, so the same database can be a
local file, an in-memory instance, or a remote server reached over the wire.
PropertyValue
Dialect nameturso
ExtendsSQLiteDialect (sqlite)
Driver@libsql/client
Cloud SDKnone
Default portnone — url
Local runtimea local libSQL file or :memory: through @libsql/client
Because libSQL's SQL is SQLite's SQL, this ORM's TursoDialect
extends SQLiteDialect and inherits every pure SQL-generation method
verbatim — DDL, JSON1 helpers, upsert syntax, LIMIT/OFFSET pagination, and
identifier quoting are all produced by the SQLite code paths. Only the pieces
that genuinely differ — the driver, connection lifecycle, query execution,
streaming, and transactions — are overridden.
Key facts (from src/dialects/turso/index.ts):
Dialect name is 'turso'; the driver library is '@libsql/client'
(not better-sqlite3, which the base SQLite dialect uses).
The whole reason this dialect exists separately from SQLiteDialect is the
driver. @libsql/client works identically for a local embedded replica
(file: / :memory: URLs) and a remote hosted Turso database
(libsql: / https: URLs plus an authToken). better-sqlite3 is
local-only.
Because it reuses SQLiteDialect's SQL generation, identifiers are
double-quoted
(escapeId('my_col') → "my_col"), exactly like SQLite —
not backtick-quoted like MySQL.
The dialect keeps entirely separate connection/transaction state from its
parent, since SQLiteDialect reaches its own connection through private
fields a subclass can't touch.

Quick start#

Install#

$ npm install ts-prorm-orm @libsql/client
$ pnpm add ts-prorm-orm @libsql/client
$ yarn add ts-prorm-orm @libsql/client
$ bun add ts-prorm-orm @libsql/client

Connect#

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

export const db = new Prorm({
  dialect: 'turso',
  dialectOptions: {
    url: 'libsql://my-db-myorg.turso.io', // or 'file:./local.db'
    authToken: process.env.TURSO_AUTH_TOKEN,
  },
});

Define a model#

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

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

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

Query#

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

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

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

Generated SQL#

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

Create table#

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

Insert, update and delete#

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

Upsert#

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

Pagination#

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

Transaction 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(() => {});
});
Type mapping for the portable descriptors: STRING → VARCHAR(255), auto-increment INTEGER → INTEGER, BOOLEAN → INTEGER, DATE → DATETIME, UUID → TEXT, JSON → TEXT. The type comparison lines the major engines up side by side.

Connection#

The dialect is created with a url (and, for hosted databases, an
authToken), not the host/port/username used by server dialects.
import { Prorm } from 'ts-prorm-orm';

// Hosted Turso database
const db = new Prorm({
  dialect: 'turso',
  dialectOptions: {
    url: 'libsql://my-db.turso.io',
    authToken: process.env.TURSO_AUTH_TOKEN,
  },
});

await db.connect();
For a local libSQL file, or an ephemeral in-memory database, drop the
authToken and point url at a file: or :memory: target:
// Local file — no auth token needed
const local = new Prorm({ dialect: 'turso', url: 'file:./local.db' });

// In-memory (the default if `url` is omitted)
const mem = new Prorm({ dialect: 'turso', url: ':memory:' });
TursoDialectOptions (all optional):
OptionPurpose
urllibsql://… / https://… (hosted), file:./… (local), :memory:.
authTokenAuth token for a hosted Turso database. Unused for file:/:memory:.
encryptionKeyEncryption key for an encrypted local database file.
syncUrlRemote database to sync an embedded replica against (see below).
syncIntervalSync interval in seconds when syncUrl is set.
Notes:
If url is omitted, it defaults to :memory:.
connect() eagerly verifies the connection by running SELECT 1 and then
PRAGMA foreign_keys = ON, so a bad URL or token fails at connect time
rather than on your first query.
A failed connection is wrapped as
Failed to connect to Turso/libSQL database: <error>.

What differs from SQLite#

TursoDialect extends SQLiteDialect (sqlite) and
overrides 18 of its methods (Object.getOwnPropertyNames(TursoDialect.prototype),
computed by the scratch test); everything else is inherited unchanged.
AreaOverridden
Connection and executioncommitTransaction, connect, disconnect, getConnection, isConnected, query, queryStream, rollbackTransaction, startTransaction
TypesmapNativeType, renderSqliteType
DDL and schemaattachDatabase, detachDatabase
IntrospectiongetDatabaseVersion
OtherrowToObject, setPragma, sync, toLibsqlArgs

SQLite compatibility#

Everything the ORM generates for Turso is SQLite SQL, inherited unchanged from
SQLiteDialect. Standard CRUD, table creation, and JSON1 helpers all behave
exactly as documented for the SQLite dialect.
await db.connect();

await db.dialect.createTable('widgets', {
  id: { type: 'INTEGER', primaryKey: true, autoIncrement: true },
  name: { type: 'TEXT', allowNull: false },
  price: { type: 'REAL' },
} as any);
Query execution accepts positional or named parameters. The dialect reads
options.replacements (falling back to options.bind), so both work:
// Positional
await db.dialect.query('INSERT INTO widgets (name, price) VALUES (?, ?)', {
  replacements: ['gadget', 9.99],
} as any);

// Named
await db.dialect.query('INSERT INTO widgets (name, price) VALUES (:name, :price)', {
  replacements: { name: 'widget', price: 3 },
} as any);
For a SELECT (or PRAGMA), query() returns { rows, rowCount, fields },
where each row is a plain object keyed by column name. For a write it returns
{ rows: [], rowCount, lastInsertRowid }, where rowCount is the number of
rows affected and lastInsertRowid is the numeric rowid of the last insert:
const res = await db.dialect.query('INSERT INTO widgets (name, price) VALUES (?, ?)', {
  replacements: ['thing', 1.5],
} as any);
res.rowCount;         // 1
res.lastInsertRowid;  // 1

Upserts and RETURNING#

Because upsert generation is inherited from SQLite, Turso uses SQLite's
INSERT … ON CONFLICT (…) DO UPDATE form. libSQL, like modern SQLite,
supports RETURNING, so the SQLite dialect's RETURNING support applies here
too — this is a real difference from the MySQL-family dialects (TiDB, MySQL)
which have no RETURNING.

Edge and embedded replicas#

The headline libSQL feature is the embedded replica: a local libSQL file
that a background process keeps in sync with a remote Turso database. Reads hit
the local copy at SQLite speed; writes and periodic pulls go to the remote.
Configure it by giving both a local url and a syncUrl pointing at the
remote:
const db = new Prorm({
  dialect: 'turso',
  dialectOptions: {
    url: 'file:./replica.db',            // local embedded replica
    syncUrl: 'libsql://my-db.turso.io',  // remote it syncs against
    authToken: process.env.TURSO_AUTH_TOKEN,
    syncInterval: 60,                    // auto-pull every 60s
  },
});

await db.connect();
To force an immediate pull of the latest remote changes into the local
replica, call sync():
await db.dialect.sync();
sync() requires a syncUrl to have been configured at connect time —
otherwise it throws
sync() requires a syncUrl to have been configured on connect. It also throws
Not connected to database if called before connect().
For an encrypted local database, pass encryptionKey:
const db = new Prorm({
  dialect: 'turso',
  dialectOptions: {
    url: 'file:./secure.db',
    encryptionKey: process.env.DB_KEY,
  },
});

Data types#

Type mapping is inherited from SQLiteDialect (getDataTypeSql). SQLite uses
dynamic typing, so these declared types are affinity hints rather than strict
constraints. Notable mappings:
ORM type descriptorGenerated SQL
{ key: 'STRING' }VARCHAR(255)
{ key: 'STRING', length: 100 }VARCHAR(100)
{ key: 'CHAR' }CHAR(1)
{ key: 'TEXT' }TEXT
{ key: 'INTEGER' }INTEGER
{ key: 'BIGINT' }BIGINT
{ key: 'DECIMAL', precision: 12, scale: 4 }DECIMAL(12,4)
{ key: 'BOOLEAN' }INTEGER (SQLite has no boolean)
{ key: 'DATE' }DATETIME
{ key: 'DATEONLY' }DATE
{ key: 'BLOB' }BLOB
{ key: 'JSON' } / { key: 'JSONB' }TEXT (JSON stored as text)
{ key: 'UUID' }TEXT
{ key: 'ENUM', values: ['a', 'b'] }TEXT CHECK("col" IN ('a','b'))
{ key: 'GEOMETRY' }BLOB
ENUM has no native SQLite type; it is emulated as TEXT with a CHECK
constraint referencing the actual column name. JSON/JSONB are stored as
TEXT and manipulated through SQLite's JSON1 functions (json_extract,
json_group_array, json_patch, json_each, etc.), all inherited from the
SQLite dialect.

Transactions#

Transactions are driven directly against the @libsql/client connection. The
first startTransaction() issues BEGIN TRANSACTION; nested calls open
SAVEPOINTs, so nested transactions map onto savepoint semantics:
const outer = await db.dialect.startTransaction();
await db.dialect.query("INSERT INTO widgets (name) VALUES ('outer')");

const inner = await db.dialect.startTransaction(); // SAVEPOINT
await db.dialect.query("INSERT INTO widgets (name) VALUES ('inner')");
await inner.rollback();  // ROLLBACK TO SAVEPOINT — keeps 'outer'

await outer.commit();    // COMMIT
Committing the outermost transaction emits COMMIT; committing a nested one
emits RELEASE SAVEPOINT. Rollback follows the same split (ROLLBACK vs
ROLLBACK TO SAVEPOINT).

Quirks and limitations#

No .advanced extension API. SQLiteDialect exposes an .advanced
getter backed by better-sqlite3's synchronous Database handle. Turso wraps
an async @libsql/client connection with no such handle, so accessing
db.dialect.advanced throws:
TursoDialect does not support the .advanced SQLite extension API (it depends on a synchronous better-sqlite3 connection). Use the standard Dialect methods instead.
Use the standard Dialect methods (query, createTable, etc.) instead.
No native server-side cursor. @libsql/client's execute() always
returns the full result set, so queryStream() falls back to the generic
LIMIT/OFFSET-paginated stream helper (the pagination SQL is inherited
from SQLite unchanged). It still streams row-by-row across multiple
round-trips, but the batching happens client-driven rather than through a
real cursor. Provide a batchSize to tune the page size:
const stream = db.dialect.queryStream('SELECT * FROM widgets ORDER BY id', {
  batchSize: 100,
});
for await (const row of stream) {
  // ...
}
getDatabaseVersion() reports the SQLite version, via
SELECT sqlite_version() — it reflects the SQLite grammar level libSQL
implements, not a Turso server build number.
foreign_keys is enabled on connect. Unlike bare SQLite (which defaults
foreign-key enforcement off), connect() runs PRAGMA foreign_keys = ON, so
foreign-key constraints are enforced by default.
ATTACH/DETACH are available via attachDatabase(path, alias) and
detachDatabase(alias), though attaching across databases is subject to
libSQL's own restrictions on a hosted deployment.

Verification status#

The behavior above is exercised in tests/dialects/turso.test.ts, which runs
against a real :memory: libSQL instance (there is no separate driver to
mock — @libsql/client is identical for local and remote). Connection,
DDL, CRUD with positional and named parameters, rowCount/lastInsertRowid,
commit/rollback/savepoint transactions, the paginated queryStream fallback,
and the .advanced guard are all verified end-to-end locally.
What is not exercised in the suite is behavior that requires a live remote
Turso deployment: hosted authToken auth, embedded-replica syncUrl syncing,
and encryptionKey handling are wired through to @libsql/client but would
need a real Turso database (or a running libSQL server) to confirm
end-to-end.

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.
Capabilityturso
Transactions atomicyes
Savepointsyes
Isolationup to SERIALIZABLE
Transaction modesread-only no; deferrable no; constraint deferral no; SQLite locking type
RETURNINGnot emitted; returning is accepted and ignored
UpsertINSERT … ON CONFLICT (…) DO UPDATE
JSON columnTEXT (JSONB → TEXT)
Vector columnF32_BLOB(3)
Array columnTEXT
WHERE builder32 operator keys; $and/$or/$not; $exists: yes; $in subquery: yes; expression operands: yes
SQL objectsfamily sqlite: triggers yes; procedures no; functions driverUdf; materialized views emulated (app); sequences no; enums check; RLS no
StreamingqueryStream() present; LISTEN absent; createExtension() present

Testing#

tests/dialects/turso.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
Trino Dialect
Next
Vertica dialect
Built with