07 · Tables A→ZE · Govern with column domains
Remove a domain
Drop a column's domain - and why it's refused while a dependent domain still points at it.
delete_column_domain removes the domain constraint from a column. It works even
when values are currently in use - but it's refused if another domain still
depends on this one.
Remove
eddytor delete domain eddytor sales orders statusdelete_column_domain(table, "status")The dependency rule
Heads up
Removing a domain fails if a dependent domain still points
at it - a hierarchical child whose parent is this
column, or a cross-table reference domain in another
table. There is no
force flag. Remove the dependent (child / reference)
domain first, then this one.So unwind hierarchies and references top-down on dependents: drop the
product_type (grandchild) domain, then subcategory (child), then category
(parent). For a reference, drop the referencing column's domain in the dependent
table before dropping the source column's domain.
Find dependents first
If you're unsure what references a domain, check usage before removing - eddytor get domain-usage / inspect with
get_allowed_values. A blocked delete tells
you something still depends on it.