From d380d9aadb8859a6f88fdb6d5e258da2e738235d Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Wed, 13 May 2026 23:01:24 +0000 Subject: [PATCH] Better docs regards EVENTS.Behavior codes and the event detail tables --- doc/src/tables/events.m4 | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/doc/src/tables/events.m4 b/doc/src/tables/events.m4 index c686092..eee4144 100644 --- a/doc/src/tables/events.m4 +++ b/doc/src/tables/events.m4 @@ -33,10 +33,21 @@ EVENTS The |EVENTS.Start| time cannot be after the |EVENTS.Stop| time. -Each of the |EVENTS.Behavior| codes has its own rules regarding what -other information must or should be present in the database in order -to retain data validity, and what each code implies about the meaning -of related data. +Each |EVENTS.Behavior| code has a one-to-one association with a table +in the database. +An ``sdb_aggression`` |EVENTS.Behavior| code is associated with the +|AGGRESSIONS| table. +An ``sdb_arrival`` |EVENTS.Behavior| code is associated with the +|ARRIVALS| table. +And so forth. +The system will generate a warning when an EVENTS row exists and there +is no related row in the table that corresponds to the row's +|EVENTS.Behavior| code. + +Each |EVENTS.Behavior| code has its own rules regarding what other +information must or should be present in the database in order to +retain data validity, and what each code implies about the meaning of +related data. The following table lists these rules and implications: .. _EVENTS_aggression_code: -- 2.34.1