AutoBE
    Preparing search index...

    Interface AutoBeDatabaseComponentFinalizeRename

    A finalize-stage rename of one table family whose root name does not carry its stored concept — a bare structural noun, a source-file artifact, a tangled or ambiguous head noun — onto the canonical business name.

    Renaming keeps the table's concept, description, and component untouched; only the name changes. Dependent child tables sharing the renamed root as their name prefix follow automatically (x -> y also moves x_items to y_items), so the family stays consistent without separate actions.

    Rename never merges concepts: when another table already models the same concept, that is an AutoBeDatabaseComponentFinalizeAbsorb with the better-named table as survivor, not a rename onto a colliding name.

    Samchon

    interface AutoBeDatabaseComponentFinalizeRename {
        name: string;
        newName: string;
        reason: string;
        type: "renameTable";
    }
    Index

    Properties

    name newName reason type

    Properties

    name: string

    The exact existing table family root to rename. Table names are matched globally; dependent child tables prefixed by this root follow automatically.

    newName: string

    The new canonical table name, keeping the configured service prefix and plural form. It must not collide with any existing table — a collision means the concept already has a table, which is an absorb, not a rename.

    reason: string

    Why the current name fails to carry the stored concept (missing owning business concept, source-export artifact, ambiguous head noun) and why the new name is the canonical business term for the SAME concept. Decided first; the rename is the conclusion of the reason, never a backfilled justification.

    type: "renameTable"

    Type discriminator for rename.

    Settings

    Member Visibility

    On This Page

    Properties