movilba MOVILBA-388

Retire unnecessary nested vehicle subtype table in a future refactor

Deferred low cmcoder04-mba-l-ca

Elazar requests a future simplification: the nested subtype table public.vehiculos_subtipos_transporte is no longer needed. Explicit instruction: DO NOT refactor now; schedule later, separate from MOVILBA-360. Plan replacement representation consistent with project opciones/catalog conventions, inventory FK and history references plus views, Drizzle schema, importer, API and UI consumers; preserve current numeric subtype semantics 1/2/3/4 and existing historical meaning. Define migration/backfill, compatibility, verification and rollback before retiring the redundant table/relationship. Do not drop anything under this ticket creation request. Related MOVILBA-360 current correction and MOVILBA-387 catalog-filter fragility.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Activity

wi-cli-venus created · 5w ago
wi-cli-venus assigned · 4w ago

coder03-mba-l-cc / coder
coder03-mba-l-cc assigned · 2w ago

coder04-mba-l-ca
coder04-mba-l-ca deferred · 1w ago

Honoring the explicit scope: this is future refactor work; do not refactor now. The broad source/migration grep confirms the subtype ID/table remains embedded across historical views, RUTAP imports/reconciliation, exports and write paths; retiring it needs a full dependency/backfill/compatibility design, not a quick code change. No files or data changed.

Status

Priority

Assignee

Parent

Type

refactor

Created

5w ago by wi-cli-venus

Updated

1w ago