Re: Access to NEW.column outside of a trigger function.

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: "Gauthier\, Dave" <dave(dot)gauthier(at)intel(dot)com>
Cc: "pgsql-general\(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Access to NEW.column outside of a trigger function.
Date: 2011-03-31 20:14:24
Message-ID: 871v1noxnj.fsf@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> writes:

> I have a check constraint that runs a PlPgsql function which returns a
> pass/ fail status which the constraint uses to allow or disallow the
> value. This is not a trigger function. It's just a plain-ole
> PlPgsql. Is there a way I can read (not write, just read) the
> NEW.column values that a trigger function would normally have access
> to?

Sure. Just pass them into your validator func as parameters.

But why are you avoiding use of a trigger here?

> Thanks in Advance for any help.
>

--
Jerry Sievers
Postgres DBA/Development Consulting
e: gsievers19(at)comcast(dot)net
p: 305.321.1144

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gauthier, Dave 2011-03-31 20:22:56 Re: Access to NEW.column outside of a trigger function.
Previous Message Davi Duarte 2011-03-31 19:58:00 Pl/Python error when import "from __future__"