On Thursday 08 December 2005 05:11, Tom Lane wrote:
>Just starting a fresh session should make the problem go away, or if
>that's not practical update the function definition using ALTER
> FUNCTION or CREATE OR REPLACE FUNCTION. (You don't need to actually
> *change* anything about the function, j
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
> On Thursday 08 December 2005 00:23, Tom Lane wrote:
>> Offhand this looks like you might have dropped and recreated the
>> event_citations table? If so it's just the known problem that
>> plpgsql caches plans and doesn't throw them away when the r
On Thursday 08 December 2005 00:23, Tom Lane wrote:
>Is there a reason you don't just mark the FK reference as ON DELETE
>CASCADE, rather than using a handwritten trigger?
I could have done that, of course. I'm still a little shaky on "best
practice" with these things. Besides, I haven't found ou
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
> I have a trigger that will delete records referring to an "events" table
> upon deletion. I have used it without problems for a number of times:
> CREATE OR REPLACE FUNCTION delete_event_cascade() RETURNS TRIGGER AS $$
> BEGIN
> DELETE FROM e
Hello,
I have a trigger that will delete records referring to an "events" table
upon deletion. I have used it without problems for a number of times:
CREATE OR REPLACE FUNCTION delete_event_cascade() RETURNS TRIGGER AS $$
BEGIN
DELETE FROM event_citations WHERE event_fk = OLD.event_id;
DE
