1. guides
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. guides

Models from an existing database

prorm models pull reads a live database and writes the model files that
describe it — for every SQL dialect prorm speaks. Each engine is read through
its own catalog, and each column type is mapped back to the exact
DataTypes.X(...) call that recreates it, with its length, precision, time
zone, array element, ENUM values, geometry SRID or vector dimensions intact.
The same machinery is a library, src/codegen, so a build script can read a
schema and generate models without the CLI.
The pipeline reads the catalog into a neutral SchemaModel, makes every
naming, typing and default decision once in the plan, and only then prints
files; each stage is exported from ts-prorm-orm/codegen and can be used on
its own.

Quick start#

model:create is an alias, and still accepts its original --out-dir,
--table and --storage flags.
The connection can also come from the environment, like every local command,
so a project that keeps its URL in .env needs no connection flags:
DATABASE_URL=postgres://app:secret@localhost:5432/app
$ prorm models pull --schema public --out src/models
FlagDefaultMeaning
--url, --dialect, --database, --host, --port, --username, --password$DATABASE_URL / DB_*The connection, as every local command takes it. --dialect accepts every SQL dialect.
--out (--out-dir)./modelsDirectory to write to.
--tables (--table)every base tableComma-separated table names. A name that does not exist is reported and skipped.
--schemathe connection's current onePostgreSQL schema, MySQL database, SQL Server schema, Oracle owner, BigQuery dataset, Snowflake schema, …
--styledefinedefine: an init<Model>(prorm) per file calling prorm.define(). class: @Table classes.
--langtsts or js. The class style is TypeScript only.
--modulecjscjs or esm, for --lang js.
--namingpreservepreserve keeps column names as attribute names; camel camelCases them with a field: mapping (see Naming).
--no-timestampsonDon't turn createdAt/updatedAt/deletedAt columns into prorm-managed timestamps.
--no-associationsonDon't generate associations from foreign keys.
--dry-runPrint the files; write nothing. With --json, the files are in the JSON.
--forceOverwrite existing files. Without it nothing is written if any target file exists.
Exit codes: 0 done, 1 refused to overwrite / generation failed, 2 usage
error, 5 every requested table was missing.

Walkthrough: a SQLite bookshop#

A small but complete run, from an existing database to models the app loads.
The output below is what the command prints for this schema.

Start from the database you have#

Pull the models#

$ prorm models pull --dialect sqlite --database ./shop.sqlite --out src/models
✓ Generated 4 model(s) from sqlite (catalog: sqlite):
  src/models/Authors.ts
  src/models/BookTags.ts
  src/models/Books.ts
  src/models/Tags.ts
  src/models/index.ts
src/
  models/
    Authors.ts    # timestamps: true, createdAt: 'created_at'
    BookTags.ts   # the join table
    Books.ts      # paranoid: true, the CHECK read back as an ENUM
    Tags.ts
    index.ts      # initModels(): every model plus the associations

Review what it inferred#

The index.ts it wrote wires every association the foreign keys imply,
including the many-to-many through the pure join table book_tags:
export function initModels(prorm: Prorm) {
  const Authors = initAuthors(prorm);
  const BookTags = initBookTags(prorm);
  const Books = initBooks(prorm);
  const Tags = initTags(prorm);

  BookTags.belongsTo(Tags, { foreignKey: 'tag_id', as: 'tag' });
  BookTags.belongsTo(Books, { foreignKey: 'book_id', as: 'book' });
  Books.belongsTo(Authors, { foreignKey: 'author_id', as: 'author', onDelete: 'CASCADE' });
  Authors.hasMany(Books, { foreignKey: 'author_id', as: 'books', onDelete: 'CASCADE' });
  Tags.belongsToMany(Books, { through: { model: BookTags, otherKey: 'book_id' }, foreignKey: 'tag_id', as: 'books' });
  Books.belongsToMany(Tags, { through: { model: BookTags, otherKey: 'tag_id' }, foreignKey: 'book_id', as: 'tags' });

  return { Authors, BookTags, Books, Tags };
}
On SQLite, status TEXT CHECK (status IN (…)) comes back as
DataTypes.ENUM('draft', 'published'), typed 'draft' | 'published' in
BooksAttributes.

Load them in the app#

import { Prorm } from 'ts-prorm-orm';
import { initModels } from './models';

export const prorm = new Prorm({ dialect: 'sqlite', storage: './shop.sqlite' });
export const models = initModels(prorm); // before connect(): see "Using the models on an empty database"
await prorm.connect();

const { Authors, Books } = models;
const author = await Authors.findOne({ where: { email: 'ada@example.com' } });
const books = await Books.findAll({ where: { author_id: author?.get('id') } });

Commit, and re-pull when the schema moves#

The files are ordinary source: commit them and edit them freely. See
Re-pulling after a schema change for
what a second run does to them.

Re-pulling after a schema change#

A second run refuses to touch anything that exists, and says which files are
in the way:
$ prorm models pull --dialect sqlite --database ./shop.sqlite --out src/models
✗ Refusing to overwrite 5 existing file(s) (pass --force to overwrite):
  /app/src/models/Authors.ts
  /app/src/models/BookTags.ts
  /app/src/models/Books.ts
  /app/src/models/Tags.ts
  /app/src/models/index.ts
$ echo $?
1
After ALTER TABLE authors ADD COLUMN bio TEXT and
ADD COLUMN verified BOOLEAN NOT NULL DEFAULT 0, regenerating that one table
prints a warning for the column it could not make portable:
$ prorm models pull --dialect sqlite --database ./shop.sqlite --tables authors --out src/models --force
! authors.verified: kept native type BOOLEAN (DataTypes.BOOLEAN() would create INTEGER on sqlite).
✓ Generated 1 model(s) from sqlite (catalog: sqlite):
  src/models/Authors.ts
  src/models/index.ts
and Authors.ts changes by exactly the new columns:
       email: {
         type: DataTypes.STRING(255),
         allowNull: false,
         unique: true,
       },
+      bio: {
+        type: DataTypes.TEXT(),
+      },
+      verified: {
+        type: 'boolean', // native: BOOLEAN — DataTypes.BOOLEAN() would create INTEGER on sqlite
+        allowNull: false,
+        defaultValue: false,
+      },
     },
[!WARNING] --tables rewrites index.ts too
The index.ts written with --tables authors registers only Authors: the
other models and every association disappear from it. Either re-pull the
whole schema with --force and review the diff in git, or regenerate one
table with --dry-run and paste the part you want. --force also discards
any hand edits in the files it rewrites.
A name that does not exist is reported, not guessed at; when nothing is left
the exit code is 5:
$ prorm models pull --dialect sqlite --database ./shop.sqlite --tables nope --dry-run
! Table 'nope' does not exist, skipping.
! Table 'nope' does not exist.
! No tables found; nothing to generate.
$ echo $?
5

What comes out#

For --style define (the default), one file per table plus an index:
// src/models/Books.ts
import { DataTypes } from 'ts-prorm-orm';
import type { Prorm } from 'ts-prorm-orm';

export interface BooksAttributes {
  id: number;
  author_id: number;
  title: string;
  price?: number | string | null;
  deleted_at?: Date | null;
}

export let Books: ReturnType<Prorm['define']>;

export function initBooks(prorm: Prorm): ReturnType<Prorm['define']> {
  Books = prorm.define<BooksAttributes>(
    'Books',
    {
      id: { type: DataTypes.INTEGER(), primaryKey: true },
      author_id: { type: DataTypes.INTEGER(), allowNull: false },
      title: { type: DataTypes.STRING(200), allowNull: false },
      price: { type: DataTypes.DECIMAL(12, 4), defaultValue: 1.5, comment: 'Net, in EUR' },
    },
    {
      tableName: 'books',
      timestamps: false,
      paranoid: true,
      deletedAt: 'deleted_at',
      uniqueKeys: [{ fields: ['author_id', 'title'] }],
      indexes: [{ name: 'ix_books_title', fields: ['title'] }],
    },
  );
  return Books;
}
// src/models/index.ts
export { Authors, initAuthors } from './Authors';
export { Books, initBooks } from './Books';

export function initModels(prorm: Prorm) {
  const Authors = initAuthors(prorm);
  const Books = initBooks(prorm);

  Books.belongsTo(Authors, { foreignKey: 'author_id', as: 'author', onDelete: 'CASCADE' });
  Authors.hasMany(Books, { foreignKey: 'author_id', as: 'books', onDelete: 'CASCADE' });

  return { Authors, Books };
}
Call initModels(prorm) once after creating the instance. For --style class
each file is a decorated class (@Table, @Attribute, @PrimaryKey,
@BelongsTo(() => Authors, …), …) and the index exports
registerModels(prorm), which calls prorm.addModel() for each.
The same tags table in both styles, as --dry-run prints them:
export interface TagsAttributes {
  id?: number;
  label: string;
}

export let Tags: ReturnType<Prorm['define']>;

export function initTags(prorm: Prorm): ReturnType<Prorm['define']> {
  Tags = prorm.define<TagsAttributes>(
    'Tags',
    {
      id: { type: DataTypes.INTEGER(), primaryKey: true, autoIncrement: true },
      label: { type: DataTypes.STRING(40), allowNull: false, unique: true },
    },
    { tableName: 'tags', timestamps: false },
  );
  return Tags;
}
import { Model, DataTypes, Table, Attribute, PrimaryKey, AutoIncrement, NotNull, Unique } from 'ts-prorm-orm';
import type { CreationOptional, InferAttributes, InferCreationAttributes } from 'ts-prorm-orm';

@Table({
  tableName: 'tags',
  timestamps: false,
})
export class Tags extends Model<InferAttributes<Tags>, InferCreationAttributes<Tags>> {
  @Attribute(DataTypes.INTEGER())
  @PrimaryKey()
  @AutoIncrement()
  declare id: CreationOptional<number>;

  @Attribute(DataTypes.STRING(40))
  @NotNull()
  @Unique()
  declare label: string;
}
Every file starts with a comment block naming the table, the table comment,
and anything the generator could not express: CHECK constraints, expression
indexes, composite foreign keys, foreign keys to tables that were not
generated, and lists the catalog could not report.

Types#

Columns are read with the dialect's own reverse mapping (mapNativeType),
which yields a canonical descriptor — the same one normalizeDataType gives a
DataTypes value. The generator writes the factory call for it:
Native (examples)Generated
character varying(100), VARCHAR2(40), nvarchar(100)DataTypes.STRING(100)
int unsigned, bigint, HUGEINT, tinyintDataTypes.INTEGER({ unsigned: true }), DataTypes.BIGINT(), DataTypes.HUGEINT(), DataTypes.TINYINT()
numeric(12,4), NUMBER(12,2)DataTypes.DECIMAL(12, 4)
timestamp(3) with time zone, datetimeoffset(3), TIMESTAMP_TZ(9)DataTypes.TIMESTAMPTZ(3)
TIMESTAMP WITH LOCAL TIME ZONE, TIMESTAMP_LTZDataTypes.TIMESTAMP({ timezone: 'local' })
enum('a','b'), a PostgreSQL enum type, SQLite TEXT CHECK (x IN (…))DataTypes.ENUM('a', 'b') (named: .setName('mood'))
integer[], INTEGER[3], ARRAY<STRING>DataTypes.ARRAY(DataTypes.INTEGER()), …, { size: 3 }
STRUCT(x INT, y VARCHAR), MAP(VARCHAR, INT)DataTypes.STRUCT({ x: …, y: … }), DataTypes.MAP(…, …)
geometry(Point,4326)DataTypes.GEOMETRY('POINT', 4326)
vector(1536), halfvec(768)DataTypes.VECTOR(1536), DataTypes.VECTOR(768, { element: 'float16' })

When the native type is kept#

The generator never degrades a type to STRING. When there is no portable
equivalent — PostgreSQL xid, a domain, an unconstrained numeric (which
DataTypes.DECIMAL() would pin to (10,0)) — it writes the native type as the
column type, verbatim, with a comment saying why:
const attributes = {
  xmin_copy: {
    type: 'xid', // native: xid — no portable DataTypes equivalent
  },
};
It also checks every portable type against the dialect it read from: the call
is rendered with that dialect's getDataTypeSql() and mapped back. If the
engine cannot create the type (SQLite has no BIT), or would create a
different column (CockroachDB's INTEGER is 64-bit; under the default
typeMapping: 'legacy' some types are created with their 4.8 spelling, e.g. a
PostgreSQL enum as VARCHAR(255)), the native type is kept so that sync()
recreates exactly the column that was read. Connect with
new Prorm({ …, typeMapping: 'modern' }) to generate portable types for
columns the legacy mapping would change — see Type mapping.

Defaults, keys and constraints#

Defaults are parsed from each engine's own spelling ('x'::text,
((0)), N'x', MySQL's bare values, CAST('t' AS BOOLEAN)) into a
constant typed by the column — '0' is 0 on an INTEGER and '0' on a
VARCHAR. An expression (CURRENT_TIMESTAMP, gen_random_uuid()) is kept as
raw SQL: prorm.literal('…') in the define style,
Prorm.prototype.literal('…') in the class style. Sequence and identity
defaults become autoIncrement: true.
Primary keys become primaryKey: true; a composite key becomes
constraints: [{ type: 'PRIMARY KEY', fields: [...] }] in the define style.
Unique constraints on one column become unique: true (or the
constraint name); composite ones become uniqueKeys (define) or unique
indexes (class, whose @Table has no uniqueKeys).
Indexes become indexes: [{ name, fields, unique, using, where }].
Indexes that back a key or a foreign key are not repeated. Expression
indexes are listed in the file comment instead.
CHECK constraints are listed in the file comment; they are not declared
(a raw-SQL check is deprecated in model options).
Comments on tables and columns become comment:.

Associations#

From each single-column foreign key:
Source.belongsTo(Target, { foreignKey, as, targetKey?, onDelete?, onUpdate? }),
the alias taken from the column (author_id → author);
the inverse on the target: hasOne when the key is unique, else hasMany,
named after the source table (books), with As<Alias> appended when two
foreign keys point at the same table (booksAsAuthor, booksAsEditor) or
the key is self-referencing.
A pure join table — exactly two single-column foreign keys, nothing but
managed timestamps besides, and no primary key or one over those two columns —
also produces belongsToMany on both ends, through the join model:
Books.belongsToMany(Tags, {
  through: { model: BookTags, otherKey: 'tag_id' },
  foreignKey: 'book_id',
  as: 'tags',
});
Composite foreign keys, and foreign keys into tables that are not being
generated (or live in another schema), are noted in the file comment.

Timestamps and soft deletes#

Columns named createdAt/created_at and updatedAt/updated_at (any case,
of a timestamp type) turn on timestamps: true, with createdAt: /
updatedAt: naming the columns when they are not the defaults; a nullable
deletedAt/deleted_at turns on paranoid: true. Those columns are then
maintained by prorm and are not declared as attributes (the class style still
declares them for typing). Pass --no-timestamps to keep them as plain
columns.

Naming#

Models are the table name in PascalCase (blog_post → BlogPost),
made safe as a class and file name: a reserved word, a global (Date,
Object) or an imported name (Model, DataTypes) gets a Model suffix; a
leading digit gets _; names that differ only in case get a number.
Attributes keep the column name by default (--naming preserve); any
name is allowed, quoted where it is not an identifier ('first name': {…}).
--naming camel writes camelCase attributes with field: 'column_name'
(@Field('column_name') in the class style). A column whose name would
shadow a model member (save, update, destroy, …) becomes
<name>Value with a field mapping in either mode. prorm reads and writes
every mapped attribute through its column — see
Column names.

Using the models on an empty database#

define() creates a model's table as soon as it runs on a connected instance
— before the associations that add its foreign keys have been declared — so
to build an empty database from generated models, either call
initModels(prorm) before connect(), or run await prorm.sync({ force: true })
once. On the database the models were read from, sync() is a no-op.

Dialect coverage#

"Full" means columns, primary key, unique constraints, indexes, foreign keys
with their actions, CHECK constraints and comments. Anything a reader cannot
see is marked unknown in the schema model (table.known) and in the file
comment, never guessed.
DialectsCatalogCoverage
SQLite, Turso, D1, rqlitesqlite_master, PRAGMA table_info / index_list / index_info / foreign_key_listFull. CHECKs are read from the CREATE TABLE text; SQLite has no comments.
PostgreSQL, TimescaleDB, Citus, YugabyteDB, Greenplum, openGauss, AlloyDB, Neon, Supabase, CockroachDB, Yellowbrick, ParadeDB, the managed PostgreSQL servicespg_catalog (format_type, pg_enum, pg_constraint, pg_index, obj/col_description)Full, including enum types, identity columns, partial and method-specific indexes. Parts an engine's pg_catalog lacks fall back to information_schema or are reported unknown (Materialize, RisingWave, Aurora DSQL).
MySQL, MariaDB, TiDB, SingleStore, OceanBase, PolarDB, Vitess, Dolt, HeatWave, Doris, StarRocks, the managed MySQL/MariaDB servicesMySQL information_schemaFull. CHECKs need MySQL 8.0.16+ / MariaDB 10.2+ (unknown before). MariaDB JSON (LONGTEXT + json_valid) is read as JSON.
SQL Server, Azure SQL / MI, Fabric, Synapse, RDS and Cloud SQL for SQL ServerINFORMATION_SCHEMA.COLUMNS, sys.indexes, sys.foreign_keys, sys.check_constraints, MS_DescriptionFull, including identity columns and filtered indexes.
Oracle, Autonomous Database, RDS for OracleALL_TAB_COLUMNS, ALL_CONSTRAINTS, ALL_INDEXES/ALL_IND_EXPRESSIONS, ALL_*_COMMENTSFull (identity columns on 12c+). Names keep their dictionary case.
Db2, RDS for Db2SYSCATFull.
SAP HANASYS.TABLES, SYS.CONSTRAINTS, SYS.REFERENTIAL_CONSTRAINTS, SYS.INDEX_COLUMNSFull.
FirebirdRDB$ system tables (columns included)Full.
DuckDB, MotherDuckduckdb_tables/columns/constraints/indexes()Full, including named ENUMs, fixed arrays, STRUCT/MAP/UNION.
Verticav_catalogKeys, foreign keys, CHECKs, comments. No indexes (projections).
ExasolEXA_ALL_*Primary and foreign keys, comments. The engine has no UNIQUE, CHECK or indexes.
TeradataDBC.*VPrimary key, UNIQUE, secondary indexes, foreign keys, comments. CHECKs unknown.
BigQuerydataset INFORMATION_SCHEMAColumns (nested STRUCT/ARRAY), descriptions, the unenforced primary and foreign keys. The engine has no UNIQUE, CHECK or secondary indexes.
SnowflakeDESCRIBE TABLE, SHOW PRIMARY/UNIQUE/IMPORTED KEYS, SHOW INDEXESColumns, identity, comments, the informational keys, hybrid-table indexes. No CHECKs (engine).
DatabricksUnity Catalog information_schemaKeys, foreign keys, CHECKs, comments. No indexes (engine).
ClickHousesystem.columns / tables / data_skipping_indicesColumns, comments, primary key, skipping indexes. No foreign keys or UNIQUE (engine); CHECKs unknown.
Redshift, Redshift Data APIinformation_schemaKeys and foreign keys. No CHECKs or indexes (engine); comments unknown.
Spanner, Spanner PostgreSQLINFORMATION_SCHEMA (+ INDEXES)Keys, foreign keys, CHECKs, indexes. Comments unknown.
Trino, Presto, Athenainformation_schemaColumns and column comments. Keys and CHECKs depend on the connector: unknown.
CrateDBinformation_schemaPrimary key, CHECKs. No foreign keys or indexes (engine).
MonetDBinformation_schemaKeys, foreign keys, CHECKs. Indexes unknown.
QuestDBdescribeTable(), table_columns()Columns and symbol indexes. No keys (engine).
DruidINFORMATION_SCHEMA.COLUMNSColumns. The engine has no keys, constraints or indexes.
Azure Data Explorer (Kusto)T-SQL INFORMATION_SCHEMAColumns. No keys or indexes (engine); docstrings are not reachable from T-SQL: unknown.
RDS Data APIthe Aurora engine's catalog (engine: 'postgres' | 'mysql')As PostgreSQL / MySQL.
A source with no SQL catalog — a NoSQL store, or a Prorm instance that is
not connected — is refused with IntrospectionUnsupportedError.

As a library#

import { Prorm } from 'ts-prorm-orm';
import { introspectSchema, generateModels, pullModels } from 'ts-prorm-orm/codegen';

const prorm = new Prorm({ dialect: 'postgres', url: process.env.DATABASE_URL });
await prorm.connect();

// 1. Read: a neutral SchemaModel.
const schema = await introspectSchema(prorm, { schema: 'public', tables: ['users', 'posts'] });
for (const table of schema.tables) {
  console.log(
    table.name,
    table.columns.map((c) => `${c.name}: ${c.nativeType}`),
  );
  if (!table.known.checks) console.log('  (CHECK constraints unknown on this engine)');
}

// 2. Generate: files in memory. Pass the dialect so types are checked against it.
const { files, warnings } = generateModels(schema, {
  style: 'define',
  lang: 'ts',
  dialect: prorm.getDialectInstance()!,
});

// Or both, plus writing (refuses to overwrite unless force: true):
const report = await pullModels(prorm, { out: 'src/models', style: 'class' });

Catching drift in CI#

Generation is pure once the schema is read, so a check can regenerate in
memory and compare with what is committed, failing the build when a migration
changed the database but nobody re-pulled:
import fs from 'node:fs';
import path from 'node:path';
import { Prorm } from 'ts-prorm-orm';
import { introspectSchema, generateModels } from 'ts-prorm-orm/codegen';

const OUT = 'src/models';

const prorm = new Prorm({ dialect: 'postgres', url: process.env.DATABASE_URL, logging: false });
await prorm.connect();
try {
  const schema = await introspectSchema(prorm, { schema: 'public' });
  const { files, warnings } = generateModels(schema, {
    style: 'define',
    lang: 'ts',
    dialect: prorm.getDialectInstance()!,
  });
  warnings.forEach((w) => console.warn(`! ${w}`));

  const stale = files.filter((f) => {
    const onDisk = path.join(OUT, f.path);
    return !fs.existsSync(onDisk) || fs.readFileSync(onDisk, 'utf8') !== f.contents;
  });
  if (stale.length) {
    console.error(`Models are out of date with the database: ${stale.map((f) => f.path).join(', ')}`);
    console.error('Run: prorm models pull --out src/models --force, and review the diff.');
    process.exitCode = 1;
  }
} finally {
  await prorm.close();
}
$ DATABASE_URL=postgres://ci:ci@localhost/app npx tsx scripts/check-models.ts
Models are out of date with the database: Authors.ts
Run: prorm models pull --out src/models --force, and review the diff.
This works only while the committed files are untouched generator output;
once you hand-edit models, compare schema against them with
SchemaDiffer instead.
Lower-level pieces are exported too: descriptorToCode(descriptor) (a
descriptor to its DataTypes call), resolveTypeCode(descriptor, { nativeType, dialect })
(the same, checked against a dialect), parseDefault(raw, type, style), and
tsString() — the one escaper every string from the catalog passes through on
its way into generated code, so a comment or ENUM value containing ', \,
a newline, */ or ${ comes out as the same text and never as code.
Modified at 2026-10-04 00:40:16
Previous
Migrations & Schema Sync
Next
Defining models
Built with