From b32fb0513857c2addb006492c8c32f08c148f657 Mon Sep 17 00:00:00 2001 From: Scott Idem Date: Mon, 18 May 2026 16:16:22 -0400 Subject: [PATCH] chore(idaa): note updated_on side effect on favorites toggle Co-Authored-By: Claude Sonnet 4.6 --- .../recovery_meetings/ae_idaa_comp__event_obj_li.svelte | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/routes/idaa/(idaa)/recovery_meetings/ae_idaa_comp__event_obj_li.svelte b/src/routes/idaa/(idaa)/recovery_meetings/ae_idaa_comp__event_obj_li.svelte index 02c3a8de..b2113dc7 100644 --- a/src/routes/idaa/(idaa)/recovery_meetings/ae_idaa_comp__event_obj_li.svelte +++ b/src/routes/idaa/(idaa)/recovery_meetings/ae_idaa_comp__event_obj_li.svelte @@ -69,6 +69,12 @@ async function toggle_favorite(event_obj: Record) { // Optimistic IDB update — liveQuery reactively re-renders the card instantly await db_events.event.update(obj_id, { mod_meetings_json: new_json }); + // NOTE: This PATCH triggers ae_event.updated_on to update (MariaDB ON UPDATE + // current_timestamp() fires on every row write). Side effect: starring a meeting + // shifts its position when sorted by updated_on, and admins see a spurious "last modified" + // timestamp. Long-term fix: either bypass ON UPDATE for this specific write (pass + // updated_on = updated_on in the SET clause server-side), or store favorites in a + // dedicated per-user table that doesn't touch the event row at all. try { await events_func.update_ae_obj__event({ api_cfg: $ae_api,