CLI FEATURE
ORM Console Toolkit
Framework credibility also lives in operations. The ORM CLI should tell you what will change before it changes anything.
Feature Guide
A quick orientation block that answers the essential questions: what this feature does, how it works, why it matters, and the key concepts behind it.
What this does
The ORM includes a practical console toolkit for schema inspection, diffing, syncing, and seeding with safe defaults.
How it works
orm:status reports server capabilities and sync state, orm:diff shows the delta, orm:sync can dry-run or export the SQL plan, and orm:seed applies defaults() upserts for seedable resources.
Why it matters
A framework should not stop at attributes and repositories. Real teams need an operational surface that explains what will happen before it changes production state.
Key concepts
- orm:status
- Reports database/server capabilities and whether the schema is currently in sync.
- orm:diff
- Shows structural differences between the code schema and the live database.
- --output
- Exports the computed SQL plan to a file for audit, review, or deployment pipelines.
Operational Surface
CLI that explains the plan before touching the database
The ORM console commands are part of the product story. They let you inspect status, review diffs, export SQL plans, and seed data without improvising custom scripts.
| Command | Purpose | Operational value |
|---|---|---|
bin/semitexa orm:status |
Show DB/server capabilities and whether schema is in sync. | Gives fast operational context before any change. |
bin/semitexa orm:diff |
List code-vs-database differences. | Lets reviewers see pending table, column, index, and FK changes. |
bin/semitexa orm:sync --dry-run |
Build the execution plan without executing it. | Safe default for CI, review, and local inspection. |
bin/semitexa orm:sync --output plan.sql |
Export the SQL plan to a file. | Useful for audit trails and DevOps handoff. |
bin/semitexa orm:seed |
Run defaults() upserts for seedable resources. | Makes local/demo environments reproducible quickly. |
Inspect current sync state
bin/semitexa orm:status
bin/semitexa orm:diff
Review SQL before execution
bin/semitexa orm:sync --dry-run -vv
bin/semitexa orm:sync --dry-run --output var/migrations/history/review.sql
Apply safe changes, then seed
bin/semitexa orm:sync
bin/semitexa orm:seed
Verified against Semitexa Ultimate 2026.09.19.1020
ORM Console Toolkit
Framework credibility also lives in operations. The ORM CLI should tell you what will change before it changes anything.
How it works
orm:status shows database capabilities and whether the schema is in sync. orm:diff lists code-versus-database differences without applying them. orm:sync --dry-run builds the execution plan as reviewable output, and --output exports it to a SQL file for audit trails. orm:seed runs defaults() upserts for seedable resources to make local and demo environments reproducible.
Why this matters
Teams that skip review tooling end up applying schema changes they did not fully understand. Treating orm:sync --dry-run as the normal review path — rather than an exotic flag — shortens incident recovery and makes schema changes safe to delegate.
How it works
orm:status reports server capabilities and sync state, orm:diff shows the delta, orm:sync can dry-run or export the SQL plan, and orm:seed applies defaults() upserts for seedable resources.
Why it matters
A framework should not stop at attributes and repositories. Real teams need an operational surface that explains what will happen before it changes production state.
Key concepts
- orm:status
- Reports database/server capabilities and whether the schema is currently in sync.
- orm:diff
- Shows structural differences between the code schema and the live database.
- --output
- Exports the computed SQL plan to a file for audit, review, or deployment pipelines.