DatabaseCopy page

database is one target named default. targets replaces it. Set one of them. The name does not set protection. NODE_ENV is not read.

okm migrate apply, okm push when it connects, provision(), okm seed, okm migrate check, and okm check when it compares a database run the host check. okm migrate plan and okm migrate status do not. Naming the URL does not refuse it.

okm migrate apply, okm push when it connects, provision(), and that same okm check comparison also read pg_backend_pid() twice. A change is OKM1854. The same opt-in skips the probe.

import { defineConfig } from "okmodel/migrate";

export default defineConfig({
  schema: "./schema.ts",
  database: process.env.DATABASE_URL!, 
});

import { defineConfig } from "okmodel/migrate";

export default defineConfig({
  schema: "./schema.ts",
  targets: {
    dev: process.env.DEV_URL!,
    prod: { url: process.env.PROD_URL!, protected: true }, 
  },
});

Protection

--allow-protected is this invocation only. It does not change the config. connect() does not read it.

verify, pull, catalog-export, and inspect have no command. okm migrate plan is plan. okm migrate status is status. okm check is check and drift. okm doctor, when roles is set, and okm ext are check. okm push is push. okm seed is seed. provision() is provision.

On okm migrate apply, the unit is backfill when it contains a backfill step. Otherwise the last contract or unclassified step sets the class. With neither, the unit is expand. A history repair rewrites a stored catalog hash. A protected target needs --allow-protected when a row changes.

okm migrate apply --target prod --allow-protected

The same database

The match is the host, the port, and the database name. The user, the password, and the query string are left out. The host is lowercased, and an omitted port is 5432, so those spellings match. The database name is not lowercased. okm check and okm migrate plan report a mismatch.

An empty database

okm migrate apply installs or replays when a head snapshot exists. With no migration files, or no head snapshot, it prints nothing to apply and does not connect. The check looks at the current schema. okm_meta, okm_history, and okm_backfill do not count as objects. A table, partitioned table, view, materialized view, sequence, foreign table, enum, domain, or extension does.