From 1323e9f0230eac5f021a4ca6a1c2d400a75dfb0d Mon Sep 17 00:00:00 2001 From: Isaac Connor Date: Sat, 16 May 2026 23:14:37 -0400 Subject: [PATCH] docs: reference the actual Event::Event constructor in lock-order block Previous wording named a fictional Event::createNotification function; the bucket+ES insert sequence in src/zm_event.cpp lives in the Event constructor (line 46). Point future readers at the right symbol so they can grep and verify the path. --- db/triggers.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/db/triggers.sql b/db/triggers.sql index 2da2b1ab3..8b622a522 100644 --- a/db/triggers.sql +++ b/db/triggers.sql @@ -127,7 +127,7 @@ drop procedure if exists update_storage_stats// * Writers that follow this order (and must continue to): * - event_update_trigger (AFTER UPDATE on Events) * - event_delete_trigger (BEFORE DELETE on Events) - * - src/zm_event.cpp Event::createNotification path: INSERT Events, then + * - The Event::Event constructor in src/zm_event.cpp: INSERT Events, then * INSERT Events_Hour/Day/Week/Month, then INSERT/UPDATE Event_Summaries * (event_insert_trigger is commented out below; zmc does it directly) * - The bucket update/delete triggers cascade into Event_Summaries in the