⌘ SchemaMap

Explore a large existing database

Start with a known legacy database table, follow FK neighbors and save an explainable investigation map.

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

    Audience and inputs

    For developers joining an unfamiliar project or returning to an old module. Bring MySQL metadata or a valid schema.json and area read access. Business records are not required. Try the synthetic shop when you have no source yet.

    Sequence

    1. Find a known table by name or column.
    2. Create an application task and sheet containing that table.
    3. Inspect columns and FKs on the right; add relevant ghosts.
    4. Use 1 step / 2 steps and collapsed groups to keep context manageable.
    5. Add explanations and a journal entry with open questions. Wait for saving.

    The result is a focused process map rather than another diagram of the entire database.

    What to validate separately

    A missing source FK does not prove there is no business relationship. An assistant may add a code-derived JOIN with evidence. Import completeness and snapshot freshness depend on the source; synchronization is manual. Investigate SQL performance with other tools. Try demo search.