Task: Add variability guards: introduce #+sql_only and #+has_qt flags to the entity schema
This page documents a task in the Decommission ores.codegen.table model type story. It captures the goal, current status, acceptance, and any notes or results.
Goal
SQL-only and Qt-less entities are expressible in ores.codegen.entity format without errors from missing C++ or Qt sections.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Decommission ores.codegen.table model type |
| Now | Complete — done via the sibling story. |
| Waiting on | Nothing. |
| Next | None. |
| Last touched | 2026-07-10 |
Acceptance
- #+sql_only: true suppresses C++ and Qt profile dispatch for the tagged entity.
- #+has_qt: false suppresses Qt profile dispatch while leaving C++ profiles active.
- generator.py raises a clear error if C++ or Qt sections are present on a sql_only entity.
- purpose_type entity file is syntactically valid with #+sql_only: true.
Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
Notes
PRs
| PR | Title |
|---|---|
Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
Result
Done — this is the same work as B5: Implement element-level physical space binding via ores.* property drawer in Resolve codegen model unification blockers, independently re-described here under a different story; no separate implementation needed.