Skip to main content

DomainApplyPlan

Defined in: js-api/src/domains.ts:788

The change plan of DomainSchemaClient.apply: what a dry run answers, and what a commit answers with applied: true (and the access effects as resolved under the lock). On an external binding the plan is registrationOnly — registry rows move, the warehouse is never touched, no live counts.

Properties​

PropertyTypeDescriptionDefined in
access?DomainAccessEffectsThe access effects, present when the body carried access.js-api/src/domains.ts:829
altersobjectTable-level toggles (audit, name column, relations, permissions), per kind.js-api/src/domains.ts:809
applied?booleanSet on the answer of a commit; absent on a dry run. false with noop: the apply changed nothing, so nothing was written.js-api/src/domains.ts:832
autoNumberChangesobjectPer table, the columns whose autonumbering changes.js-api/src/domains.ts:807
businessKeyChangesobject[]Tables whose business key changes.js-api/src/domains.ts:805
constraintDropsunknownDeclared constraints dropped.js-api/src/domains.ts:811
createsobjectWhat the apply creates: tables by name, and per table its new columns, uniques and constraints.js-api/src/domains.ts:794
creates.columnsobject-js-api/src/domains.ts:794
creates.constraintsobject-js-api/src/domains.ts:795
creates.tablesstring[]-js-api/src/domains.ts:794
creates.uniquesobject-js-api/src/domains.ts:794
destructivebooleanWhether the plan drops data, constraints or registrations — confirmDestructive needed.js-api/src/domains.ts:792
dropsobjectWhat the apply drops; liveRows / nonNullValues on a platform-stored schema only.js-api/src/domains.ts:797
drops.columnsobject[]-js-api/src/domains.ts:797
drops.tablesobject[]-js-api/src/domains.ts:797
extVersion?numberPackage-managed schema: the extension version the apply moved to.js-api/src/domains.ts:837
keyColumnsUnrestrictedDomainColumnTarget[]Restricted columns of an external target that are now key columns — visible to everyone again, since the row id encodes them.js-api/src/domains.ts:818
lost?DomainApplyLostUser-managed schema: what the drops purge or break.js-api/src/domains.ts:824
metadata?objectUser-managed schema: the schema-level metadata that changes, {from, to} per key (friendlyName, description), so a rename-only plan is not empty.js-api/src/domains.ts:827
migration{ changes: unknown[]; down: string; from: string; to: string; up: string; } | nullThe registered-snapshot transition with its migration scaffold; null when none applies.js-api/src/domains.ts:820
noop?trueSet on the answer of a commit that found nothing to change — the schema already holds what the body declares: nothing is written and version stays the one the apply was made against.js-api/src/domains.ts:835
refusalsDomainManifestIssue[]Manifest issues that refuse the plan (empty on an answered plan — a refusal rejects).js-api/src/domains.ts:815
registrationOnly?trueExternal binding: registry rows only, no warehouse DDL and no row counts.js-api/src/domains.ts:822
requiredTogglesobject[]Columns turned required or optional, with the rows a NOT NULL would refuse.js-api/src/domains.ts:803
typeChangesobject[]Columns whose type changes.js-api/src/domains.ts:799
uniqueDropsobject[]Unique constraints dropped.js-api/src/domains.ts:801
versionstringThe manifest version the apply registers.js-api/src/domains.ts:790
violationsunknown[]Data pre-checks a destructive change would violate.js-api/src/domains.ts:813