▣ wi

#98 · pluto

EAV audit — evaluar columnas DB para migración a patrón EAV

(ex-PLAN #29)

Ref
#98 (#98)
Project
pluto
Status
done
Priority
someday
Type
refactor
Assigned
— db
Created by
pluto-pm-cc-w
Created
2026-05-01T01:56:38.389Z
Updated
2026-05-15T07:32:13.130Z
Closed
2026-05-15T07:32:13.130Z

Sub-items (0/4 done · 0%)

reftitlestatuspriorityassignee
PLUTO-102 D8 Tier-1: collapse fan-out-vs-pool on 4 hot pages (admin/usuarios:97 8-wide, a-solucionar:37 6-wide, practicas:188/249, alumnos/[id]:86) via bundle-RPC/CTE per PLUTO-97 backlog high db-pluto-cc
PLUTO-99 D8 Tier-2: compute-in-Node over DB rows (cron practicas-kpi-report:277/330/146/208, legacy-export-actions:68-88, hierarchy-utils:22-74/team-stats) -> SQL GROUP BY/ORDER BY backlog normal —
PLUTO-101 D8 views+indexes (db lane): a-solucionar 6-scan view, academic-hierarchy + practicas team-stats/hierarchy views; verify 8d index candidates (deletedAt partial, periodoId, assignment*Id, comisionId/jtpId/adjuntoId, appEvents.createdAt, authId) vs actual index inventory backlog normal —
PLUTO-100 D8 Tier-3: batch sequential per-row write loops (personas-actions:378/388 role add/remove) into set-based INSERT VALUES / UPDATE WHERE id=ANY backlog low —
+ Add sub-item

Questions

No questions.

Event log