⌘ SchemaMap

Plan a task’s future structure

Show future tables, columns, relationships and indexes alongside the source structure. A task-wide plan does not execute migrations.

SchemaMap 0.14.0 · Updated · The editor uses Russian UI labels, shown as written.

    What belongs to the plan

    Planning is an available product feature: future tables, columns, indexes and relationships carry a «ПЛАН» (PLAN) marker and are available across all sheets of the task. The source area snapshot remains separate. SQL and migration file names are descriptive metadata; apply database migrations with your usual tools outside SchemaMap.

    Discuss a change

    1. Create a separate task and save a baseline sheet.
    2. Ask the connected assistant to read current IDs and revisions with analysis_get.
    3. Submit the task plan with analysis_batch and revision checks. For example, add a fictional cancelled_by_id order column and planned relationship.
    4. Open the sheet and inspect markers, JOINs and the stated goal.

    The result is a reviewable future structure on the map, without modifying the source database. REST/MCP contracts define exact arguments; there is no SQL execution step in the interface.

    Validation and preservation

    Changing or clearing the shared plan validates dependent sheets. Dangling JOINs and incompatible moves return conflicts identifying the sheet; links are not silently deleted. Read the current task and resolve dependencies in one coherent change. Individual sheet history does not undo the common plan. A legacy API view ID addresses a sheet, but changing migration still updates its parent task plan.