| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
| Cc: | pgsql-sql(at)lists(dot)postgresql(dot)org |
| Subject: | Re: functions allowed in CHECK constraints |
| Date: | 2018-02-09 14:06:31 |
| Message-ID: | CAKFQuwZx-jXU56MoYrnZ4fKn++_-XOHYgAM4--sMHS=8gJzeEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Fri, Feb 9, 2018 at 4:23 AM, Achilleas Mantzios <
achill(at)matrix(dot)gatewaynet(dot)com> wrote:
> On 09/02/2018 11:04, Achilleas Mantzios wrote:
>
>> Hello,
>>
> well it seems the intuition by reading the docs was correct, although not
> exactly explicit. A Trigger is the way to do this.
>
>> ....
>>
>
>
I answered this on the first email you sent. Functions are black-boxes so
its up to the author to ensure that the restrictions on check constraints
remain met when using them.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-09 14:32:16 | Re: functions allowed in CHECK constraints |
| Previous Message | David G. Johnston | 2018-02-09 13:58:52 | Re: functions allowed in CHECK constraints |