Ticket: HEL-684
comment column from comments sourceDate: 2026-04-04
Change sources/postgres_heroku/comments.sql from SELECT * to SELECT id, note_type, and remove the comment column from the tutor dashboard query. The comments.parquet file shrinks from 44MB to ~1MB.
The comment column in the comments table stores full free-text session notes and emails (avg 2,315 chars/row, max 99KB). With 157,799 rows, this inflates comments.parquet to 44MB — downloaded to the browser on every visit to payroll, chargeability, and tutor dashboard. No active page displays the raw comment text in payroll or chargeability. The tutor dashboard shows it in a "Last Comment" column which can be dropped since tutor_notes already provides a Last Note column covering the same need.
sources/postgres_heroku/comments.sql: SELECT * → SELECT id, note_typepages/Service Delivery/Tutors/tutor_dashboard.md:
COM.comment from the last_student_meeting query (lines 32, 35) — simplify to a plain SELECT from student_hours_transaction_logs with no JOINLSM.comment AS comment from the tutor_by_case_load SELECT (line 97)LSM.comment from the tutor_by_case_load GROUP BY (line 116)<Column id=comment title="Last Comment"/> from the DataTable (line 145)npm run build to verify clean buildsources/postgres_heroku/comments.sql — SELECT * → SELECT id, note_typepages/Service Delivery/Tutors/tutor_dashboard.md — remove comment JOIN and columnpages/Finance/payroll_export.md — no changes needed (only uses note_type, unaffected)pages/Finance/chargeability.md — no changes needed (only uses note_type, unaffected)comments.parquet is under 2MB after rebuildnpm run build passes clean