ERD Save and Change Tracking
NeoSQL saves ERD layout and table-structure changes together. Save, restore, and database apply are separate actions, so use each one for the right situation.
What Gets Saved
ERDs save information such as table positions, groups, memos, node display settings, and viewport position. Tables save structural information such as names, columns, defaults/generated expressions, keys, indexes, and constraints.
| Target | Saved Content |
|---|---|
| ERD screen | Table positions, column widths, memos, groups, and display settings |
| Table structure | Table name, description, columns, defaults/generated columns, PK, FK, indexes, and constraints |
| Viewport | Canvas position and zoom level |
Change Indicators
When structures such as table names, columns, indexes, or relationships change, add/modify/delete states appear on the table node and detail panel. Changed indexes are handled in the same save, restore, and database-apply flow.
Removing a table from the ERD is different from deleting the actual database table. Remove from ERD only removes it from the diagram, while Delete Table is a change that can be deleted when applying to DB.
Save and Restore
Save in the right info panel saves the entire ERD. Save and Restore on a table node are used to save or revert changes for the selected table.
| Action | Description |
|---|---|
| Save ERD | Saves the ERD title, table layout, display settings, and included table information. |
| Save Table | Saves the changed structure of the selected table. |
| Restore | Reverts unsaved changes to the previous state. |
| Pull Table Info | Fetches the latest table information from the actual database again. |
Conflicts with Other Users' Changes
In online mode, the same ERD may be saved first from another screen or by another user. In this case, saving from the current screen is blocked and you are guided to reload the latest state before reviewing your changes.
When editing a team ERD or shared ERD, check change indicators and recent modification status before saving. If a conflict notice appears, reload first and reapply only the necessary changes.
Check Before Applying to DB
When you run Apply Changes to DB, review the change summary and DDL preview before applying. It can include new tables, column changes, FK changes, index changes, and table rename/drop operations.
On production databases, first check whether the changes include hard-to-revert operations such as deletion or renaming.