Existing table name to erase.
Evidence and canonical-table reasoning for erasure.
OptionalseparatePrefix-named sibling tables to KEEP out of this erase's cascade because they model a DISTINCT lifecycle (their own request/return/audit/history/ event rows) the erased family does not own. Empty or absent means the cascade is unrestricted — every prefix-named descendant is erased.
Discriminator for table revision type.
Erase an existing component table.
Erasure cascades to dependent table names whose ordered singular tokens extend the erased table name. The root erase has final priority over keep, update, or create revisions in the same table family.
Author
Samchon