NeoSQL ERD Overview
Summarizes ERD fundamentals and the broad scope NeoSQL covers across data modeling, schema design, and database application workflows.
What an ERD Is
An Entity Relationship Diagram is a visual blueprint of the tables, columns, keys, indexes, constraints, and relationships that make up a database. It helps you review where data is stored, which rules protect it, and how tables reference each other.
| Element | Meaning | What to Review |
|---|---|---|
| Table | The largest unit that stores business data. | Check whether each table has a clear responsibility and is not carrying too many unrelated roles. |
| Column | An individual data field stored inside a table. | Check whether data type, nullability, default value, and comments match the actual meaning of the data. |
| Key | A rule used to identify rows or reference another table. | Check whether the PK is a stable identifier and each FK points to the correct parent table and columns. |
| Index | A structure that supports query performance, sorting, and lookup patterns. | Check whether it matches frequent query conditions and whether duplicate indexes can be removed. |
| Constraint | A database-level expression of rules that data must follow. | Check whether rules such as UNIQUE and CHECK are represented in the database, not only in application code. |
| Relation | A visual representation of reference direction and connection structure between tables. | Review relation direction, required/optional references, and the impact of update/delete actions. |
What NeoSQL Covers
NeoSQL ERD is not just a drawing tool. It is a design, review, and application tool connected to real database schemas. The tables and properties arranged on the canvas become the basis for DDL generation, Reverse/Forward Engineering, and change tracking.
| Scope | Description |
|---|---|
| Logical / Physical Modeling | Design tables, columns, data types, keys, indexes, constraints, and relations from the ERD canvas and detail panels. |
| DBMS-Specific Schema Representation | Handle types and selected special attributes for MariaDB, MySQL, Oracle, PostgreSQL, SQL Server, H2, and other supported DBMS targets. |
| Reverse / Forward Engineering | Import schemas from an existing database into an ERD, or generate DDL from ERD changes and apply it to a real database. |
| Save and Change Tracking | Track and review design changes through ERD save behavior, change detection, and revision-based review. |
| Outputs | Create shareable or actionable outputs such as ERD images, DDL, and schema change comparison results. |
| Not Covered on This Page | Button locations, shortcuts, table/column editing steps, and detailed index/constraint settings are covered step by step in the detailed ERD guides. |
Key Points
These concepts are useful to distinguish before working with NeoSQL ERD.
| Point | Description |
|---|---|
| Difference from General Diagram Tools | NeoSQL ERD is not just a drawing surface. It is a schema design screen connected to table structure, constraints, DDL, and database application workflows. |
| Main Managed Objects | NeoSQL ERD manages tables, columns, PK, FK, indexes, UNIQUE/CHECK constraints, relation lines, categories, and memos. |
| Supported DBMS | NeoSQL represents types and schema attributes for multiple DBMS targets including MariaDB, MySQL, PostgreSQL, Oracle, SQL Server, and H2. |
| Reverse and Forward | Reverse imports an existing database schema into an ERD. Forward generates DDL from ERD changes and applies it to a real database. |
| Save and Change Tracking | ERD edits are separated into save, change detection, revision review, and database application steps so changes can be reviewed before being applied. |
Features Covered in This Guide
The ERD guide is organized around the workflow from screen controls to database application.
Create ERDs and Control the Canvas
Create and open ERDs, then use canvas controls such as pan, zoom, selection, and auto-layout.
Design Table Nodes and Columns
Add tables and edit names, descriptions, columns, data types, default values, and nullability.
Manage Keys, Indexes, and Constraints
Manage PK/FK, Unique, regular indexes, Check, Exclusion, and related rules from the detail panel.
Define and Visualize Relations
Create Foreign Key based relationships and inspect the table reference structure through relation lines.
Import and Export
Import existing schemas through Reverse Engineering or export ERDs as images, DDL, and other usable outputs.
Save, Track Changes, and Apply to DB
Save ERD changes, review revisions, and use Forward features to apply changes to a real database.
Categories, Search, and Right Panels
Group tables with categories, find objects with search, and inspect ERD information or table details from the right panel.
Review DBMS-Specific Differences
Design with DBMS-specific differences in mind, including data types, auto increment behavior, constraints, and index options.
Main Screen Areas
The NeoSQL ERD screen is divided into the left navigation panel, central canvas, tool bar, mini map, and right detail panel.
| Area | Description |
|---|---|
| Left Panel | The starting point for database connections, schema/table lists, ERD lists, and dragging tables onto the canvas. |
| Canvas | The main workspace where table nodes are placed and relationship lines are reviewed. Pan, zoom, selection, and layout actions happen here. |
| Tools | Provides canvas tools such as select, add table, create relation, memo, zoom, fit view, and lock. |
| Mini Map | Shows a reduced view of the full ERD layout so you can quickly understand the current position in a large diagram. |
| Right Panel | Shows ERD information, display options, included tables, and detailed properties for the selected table. |