What this screen does
The Database tab shows the relational schema derived from your entity diagram: one table per entity, foreign keys for relationships, and pivot tables where many-to-many relations need them. You normally do not draw here — you regenerate from the entities and review the result.
Typical workflow
- After changing the Entities tab, click Regenerate from Entities to rebuild the schema. Table and column names follow Laravel conventions automatically.
- Review the tables: check that foreign keys point the way you expect and that pivot tables appeared where you expect them.
- Need something the entity model does not express — a lookup table, an import staging table? Add Custom Table creates one that survives regeneration.
- Generate SQL produces the schema as SQL statements; Text View gives a compact textual listing for review.
- Reset Positions tidies the layout if dragging left it messy.
Examples & tips
- Treat this tab as a review checkpoint, not an editor. If a column is wrong, fix the attribute on the Entities tab and regenerate — edits made here to derived tables are overwritten by the next regeneration.
- Custom tables are the exception: they are yours and persist across regenerations.
- A missing pivot table almost always means the relationship on the Entities tab is typed one-to-many when you meant many-to-many.