From 4a4b893d84ed5a85282c293268f58d9993766a9f Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Mon, 1 Jun 2026 17:30:22 +0000 Subject: [PATCH] Shorten EVENTS.Behavior constraint name to fit within limits Unfortunately, there is not enough space to list the allowed behavior codes. The user will just have to refer to the documentaion when they violate the constraint. --- db/schemas/sokwedb/tables/create/events.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/db/schemas/sokwedb/tables/create/events.m4 b/db/schemas/sokwedb/tables/create/events.m4 index 577a7e7..78ef425 100644 --- a/db/schemas/sokwedb/tables/create/events.m4 +++ b/db/schemas/sokwedb/tables/create/events.m4 @@ -30,7 +30,7 @@ CREATE TABLE events ( ,atid INTEGER REFERENCES attendance ,behavior TEXT NOT NULL - CONSTRAINT "Behavior must be one of: sdb_aggression, sdb_arrival, sdb_food, sdb_grooming, sdb_groom_scan, sdb_mating, sdb_other_species, sdb_pantgrunt" + CONSTRAINT "Behavior must be one of the allowed special values" CHECK (behavior IN ('sdb_aggression' , 'sdb_arrival' , 'sdb_food' -- 2.34.1