From 8343cc39d0b6702efae8a07add9bc54eb1c1bd26 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Mon, 25 May 2026 17:53:15 +0000 Subject: [PATCH] EVENTS.Start and Stop have semantics that depend on the behavior --- doc/src/tables/events.m4 | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/src/tables/events.m4 b/doc/src/tables/events.m4 index 8b14813..6715e42 100644 --- a/doc/src/tables/events.m4 +++ b/doc/src/tables/events.m4 @@ -295,6 +295,10 @@ The "starting minute" recorded in this column is an "inclusive endpoint", the event occurred (or began occurring), and was ongoing, during the designated minute. +That said, the precise semantics of this column depend on the +:ref:`type of event ` being recorded -- the +EVENTS.\ |EVENTS.Behavior| value. + The value of this column cannot be before ``sdb_min_event_start``. |noseconds| |notnull| @@ -313,6 +317,10 @@ The "ending minute" recorded in this column is an "inclusive endpoint", the event finished occurring, but was ongoing, during the designated minute. +That said, the precise semantics of this column depend on the +:ref:`type of event ` being recorded -- the +EVENTS.\ |EVENTS.Behavior| value. + The value of this column cannot be after ``sdb_max_event_stop``. |noseconds| |notnull| -- 2.34.1