From: | Josh Trutwin <josh(at)trutwins(dot)homeip(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Question about no unchanging update rule + ALTER |
Date: | 2009-02-27 16:06:35 |
Message-ID: | 20090227100635.283586b1@prokofiev.trutwins.homeip.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 27 Feb 2009 09:34:08 +0000
Richard Huxton <dev(at)archonet(dot)com> wrote:
> > CREATE TRIGGER prevent_empty_updates BEFORE UPDATE ON test FOR
> > EACH ROW EXECUTE PROCEDURE prevent_empty_updates();
> >
> > Actually after writing this, this TOO does not seem to work after
> > an ADD COLUMN. :/ Any suggestions?
>
> Try disconnecting and reconnecting to the database - that should do
> it. The function will be "compiled" the first time it is called in
> a session , so the * is probably getting expanded then. There's
> been a lot of work done to provide automatic re-planning in these
> sort of situations, but maybe you're hitting a corner-case.
Thanks for the info - I'll test out the disconnect and report back.
Josh.
From | Date | Subject | |
---|---|---|---|
Next Message | Enrico Sirola | 2009-02-27 17:00:03 | when to use "execute" in plpgsql? |
Previous Message | Joshua D. Drake | 2009-02-27 16:01:34 | Re: Standalone ODBC Driver |