Task: Rename the curve configuration tables with a _config suffix
Table of Contents
This page documents a task in the Model the ORE report configuration as entities story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
Rename the per-entry curve configuration tables so each name says it holds configuration: yield_curve becomes yield_curve_config, fx_volatility becomes fx_volatility_config, and so on. curve_definition, the header row other documents refer to, keeps its name.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Model the ORE report configuration as entities |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-03 |
3. Acceptance
- Every per-entry curve configuration table, and its C++ type, repository, protocol, shell commands and permissions, carries the _config suffix.
- curve_definition, the child tables and the tables whose names already say configuration keep their names.
- Every corpus curveconfig.xml still round trips, in memory and through the database.
4. 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.)
5. Measurements
Every number this task claims about a tree, with the command that produced it
and the commit it was measured at. A number without both is not a measurement,
because a clean-up record describes a tree and trunk moves under a branch: a
consumer count, a gate's component count and a suite's size all change with no
code changing, and the reader of a bare number cannot tell which tree it came
from. Where the raw output matters, put it in an evidence/ file beside the
task and name that file in the Command column.
| What | Value | Command | Commit |
|---|---|---|---|
6. Notes
7. Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario)
that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
8. PRs
| PR | Title |
|---|---|
| #2571 | [refdata] Rename the curve configuration tables with a _config suffix |
9. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
10. Result
The eighteen per-entry curve configuration entities now carry the _config
suffix in every layer: table (ores_refdata_yield_curve_configs_tbl), C++ type
and repository (yield_curve_config, yield_curve_config_repository),
protocol, shell commands, recipes and permission codes. They are the yield,
equity, default, inflation, commodity and intraday power curves, securities,
the FX, yield, CDS, inflation cap and floor, swaption, cap and floor, equity,
commodity and bond future volatilities, and the base and curve correlations.
curve_definition, the child tables and the tables whose names already said
configuration kept their names.
The rename is reproducible: a script renders the renamed models from the same specs that produced them (the eighteen committed models matched their specs exactly first), removes the 702 files the old names generated, as listed by the generator itself, regenerates, and rewrites the hand-written references in the mapper, its tests and the SQL entry points.
Verified: build clean; database recreated; ctest 90/90, including the whole-document corpus walk and the database round trips.
No migration: on the operator's instruction a database is trashed and recreated rather than migrated, and no backwards compatibility code is kept. The same change removed the thirteen migration scripts this story had added (the curve configuration steps, the report type binding, the stress shift vocabulary and the today's market collection kinds).