From: | CSN <cool_screen_name90001(at)yahoo(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | not null error in trigger on unrelated column |
Date: | 2005-11-22 03:54:54 |
Message-ID: | 20051122035454.92670.qmail@web52909.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have a members table and an items table. Every time items.member_id or items.active gets
changed, members.items_submitted and members.items_approved gets updated by a trigger on items. I
added an "admin" column to members, and now this happens:
=> update items set active = false where member_id=38;
ERROR: null value in column "admin" violates not-null constraint
CONTEXT: SQL statement "update members set items_approved=items_approved-1 where id= $1 "
PL/pgSQL function "update_member_item_counts" line 54 at SQL statement
The relevant part of the (after) trigger function on items is:
ELSIF OLD.active is true and NEW.active is false then
update members set
items_approved=items_approved-1
where id=NEW.member_id;
END IF;
Is it necessary to drop and recreate triggers and/or corresponding functions after changing a
table's schema? I don't know how something is trying to set members.admin to null (table members
has no triggers).
thanks
csn
Postgresql 8.0.x
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | sconeek | 2005-11-22 04:05:57 | Java, postgres and jasper help |
Previous Message | Dennis Veatch | 2005-11-22 01:29:33 | Re: Best way to represent values. |