From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: review: CHECK FUNCTION statement |
Date: | 2011-12-13 15:37:30 |
Message-ID: | 27980.1323790650@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2011/12/13 Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>:
>> Either that, or couldn't you pass an option List as data type "internal"?
> this is question - internal is most simply solution, but then we
> cannot to call check function directly
Yeah, one of the proposals for allowing people to specify complicated
conditions about what to check was to tell them to do
select checker(oid) from pg_proc where any-random-condition;
If the checker isn't user-callable then we lose that escape hatch, and
the only selection conditions that will ever be possible are the ones
we take the trouble to shoehorn into the CHECK FUNCTION statement.
Doesn't seem like a good thing to me.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2011-12-13 15:40:49 | Re: JSON for PG 9.2 |
Previous Message | Torello Querci | 2011-12-13 15:33:50 | Re: pg_cancel_backend by non-superuser |