Isaac Connor 19c5bcbbde docs: correct Event::delete lock-order comment to match triggers.sql ...

The previous comment block claimed event_update_trigger fires BEFORE UPDATE
and that the lock order was buckets -> Event_Summaries -> Events. Neither
matches the code: triggers.sql defines event_update_trigger as AFTER UPDATE,
and InnoDB X-locks the matched Events row during WHERE evaluation before
either BEFORE or AFTER trigger bodies fire — so the canonical chain is
  Events[Id] -> buckets[EventId] -> Event_Summaries[MonitorId]
which is what triggers.sql already documents. Comment-only change.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-07 09:39:08 -04:00

..

lib

docs: correct Event::delete lock-order comment to match triggers.sql

2026-05-07 09:39:08 -04:00

CMakeLists.txt

build: add selective man3 generation for audited Perl modules

2026-02-15 14:47:42 -06:00

INSTALL.SKIP

glob ptz scripts under control folder

2014-01-01 12:17:13 -06:00

MANIFEST.SKIP

glob ptz scripts under control folder

2014-01-01 12:17:13 -06:00