⌘ SchemaMap

Import, synchronize and export

Supported inputs include MySQL metadata through the server adapter and schema.json/view.json; learn PNG/SVG export and portability limits.

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

    Verified input paths

    The direct server adapter reads MySQL metadata: tables, columns, indexes, FKs and SQL VIEWs. The source must be reachable from the SchemaMap server; browser localhost and server localhost are different. Use a separate account with minimal metadata-reading permissions. Credentials are handled by the server and excluded from exports.

    Another path is normalized schema.json through «База данных → Импорт JSON» (Database → Import JSON) or REST/MCP. Namespaces and stable IDs do not establish direct PostgreSQL, MariaDB or arbitrary database connector support. PostgreSQL is SchemaMap’s internal storage. A direct PostgreSQL connector, arbitrary SQL dump loader and ready-made Adminer plugin are not advertised here.

    Refresh without losing layout

    1. Export the current JSON and verify the selected area.
    2. Open «База данных» (Database) in the user menu and connect MySQL or choose import.
    3. For an existing connection, click «Синхронизировать» (Synchronize) and read «Результат» (Result).
    4. Inspect added and missing objects, then reopen a saved sheet.

    Matching IDs retain positions, pins and compatible work. Renames count as removal and addition. There is no background source polling. Invalid JSON syntax shows «Не удалось разобрать JSON. Проверьте синтаксис файла.» (Could not parse JSON. Check file syntax); connection failures show the connection error. The current map is preserved; do not replace it with an empty import. Plan/sheet dependency conflicts require reconciliation, not automatic deletion. For MCP refresh with preservation, use the documented preserveViews option.

    What an export contains

    schema.json transfers structure; view.json transfers a sheet document with task and plan context. These are not a complete account backup or membership transfer. The export button or view_render produces PNG/SVG. Local filters, open tabs and personal camera settings do not grant recipients any rights.

    Screenshot galleries and synthetic examples are stored separately and excluded from schema/view, offline and public demo exports. Private download links require current access and expire. Publishing a temporary demo is a separate explicit action using safe materials, not an automatic export of a private area.