Soft-borrar un vehiculo deja viva su fila de vehiculo_historial (ABC1234, YAM567) y la lista de dominios de prueba no lo ve
MOVILBA-193 declara dominios de prueba clavando en vehiculos VIVOS. ABC1234 (vehiculo_id 6059) y YAM567 (6060) tienen el vehiculo SOFT-DELETED y sin embargo conservan una fila VIVA en vehiculo_historial: son invisibles a la lista declarada y aun asi aportan filas vivas al censo. Dos mitades: (1) convencion - el gate tiene que leer historial ademas de vehiculos, o la lista necesita una seccion propia; (2) LA MAS IMPORTANTE - soft-borrar un vehiculo NO soft-borro su fila de vehiculo_historial. Existe trg_cascade_soft_delete_vehiculo (AFTER UPDATE, ROW) que deberia cerrar el periodo. Si un vehiculo soft-deleted puede conservar historial vivo, lo mismo vale para vehiculos REALES, no solo para datos de prueba: verificar el alcance sobre toda la tabla, no sobre estos dos. Evidencia de que son de prueba: ABC1234 chasis '1030303030' motor '131'; YAM567 chasis '10101010101010' motor '8888888888888888888'. AA111EE ya se declaro en tools/rutap-dominios-prueba.json.
Activity
-
db04-mba-l-ca
-
db04-mba-l-ca 2026-09-24 04:05 ART — SELECT-only installed-object check in DEV movilba_dev and PROD movilba: to_regclass('public.vehiculo_historial') is NULL in both; the ticket's historical population/column premise cannot be reverified in that retired table. Current replacement rutap.vehiculo_historial_normalizado has 5528 nondeleted imported rows in each base, but this sweep did not exercise the ticket-specific invariant against it. Status unchanged; do not apply an old-table repair.
-
db03-mba-l-cc / db
-
db03-mba-l-cc 2026-10-05 15:27 ART - CLOSED, measured SELECT only, PROD then DEV. (2) Cascade: trg_cascade_soft_delete_vehiculo AFTER UPDATE WHEN old.borrado_en IS NULL AND new.borrado_en IS NOT NULL, function fn_cascade_soft_delete_vehiculo, now closes BOTH vdc and rutap.v_vehiculo_historial_normalizado_fuente_actual (installed by the movilba91 cascade migrations of 2026-08-26 and the 441 repair). Body is semantically identical in PROD and DEV (md5 differs only by a DEV comment and whitespace), enabled 'O' in both. Population across the WHOLE table, not just the two: vehiculos soft-deleted 0/0; vhn rows of a soft-deleted vehiculo 0/0; vhn rows with no vehiculo 0/0 (FK vehiculo_historial_normalizado_vehiculo_id_fkey). (1) Test domains ABC1234 and YAM567 do not exist in either base, so the convention gap has nothing to apply to. NOT EXERCISED: a live soft-delete firing the cascade (it would be a write; the trigger def and body are the evidence).