Validation & problems
EntityFlow validates your schema continuously, in a background worker, so checks never block your editing. A Problems count sits in the status bar; click it to open the list.
Click any problem to select and focus its target on the canvas, so you can fix it straight away.
Severities
Problems are graded error, warning, or info.
Rules
| Rule | Severity | What it catches |
|---|---|---|
table-no-fields | error | A table needs at least one field |
duplicate-table-name | error | Two tables share a name |
duplicate-field-name | error | Two fields in one table share a name |
orphaned-ref | error | A relationship references a missing table or field |
fk-type-mismatch | warning | A foreign key links incompatible types |
increment-non-numeric | error | Auto-increment is set on a non-numeric type |
enum-type-missing | error | A field uses a type that is neither a dialect type nor a defined enum |
reserved-keyword | warning | A name is a reserved keyword in the dialect |
table-no-primary-key | warning | A table has no primary key |
cyclic-fk | warning | A foreign key participates in a reference cycle |
:::note Dialect-aware Validation is dialect-aware — type compatibility and reserved keywords are evaluated against the diagram's target dialect, so switching dialects can change which problems appear. :::