Re: Is record handle available to a check constraint stored procedure call?

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Is record handle available to a check constraint stored procedure call?
Date: 2012-03-25 09:05:54
Message-ID: jkmn5i$g5g$1@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2012-03-23, Gauthier, Dave <dave(dot)gauthier(at)intel(dot)com> wrote:
> --_000_0AD01C53605506449BA127FB8B99E5E10C358B82FMSMSX105amrcor_
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> v8.3.4 on Linux
>
> I have a check constraint on a column. The constraint decides pass/fail ba=
> sed on the returned status of a stored procedure call that returns either "=
> OK" or "NO". So when the stored procedure is called, there's a living atte=
> mpt to insert or update a record.
>
> Question: Is there a handle on the record being inserted or updated? Some=
> thing like what's available in a trigger function (new.col1, old.col2, etc.=
> ..)? If so, what does it look like?

it looks like the name of the table

create function somefunc( a foo ) returns boolean as
$$ begin return a.id <> 7 ; end $$ language plpgsql;

alter table foo add check ( somefunc(foo));

--
⚂⚃ 100% natural

In response to

Browse pgsql-general by date

  From Date Subject
Next Message François Beausoleil 2012-03-25 13:13:52 Re: Streaming replication and empty databases
Previous Message Guillaume Lelarge 2012-03-25 08:50:14 Re: can these queries be combined into one?