Re: Constraint documentation

From: Lætitia Avrot <laetitia(dot)avrot(at)gmail(dot)com>
To: coelho(at)cri(dot)ensmp(dot)fr
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Constraint documentation
Date: 2018-06-25 14:02:06
Message-ID: CAB_COdg-504-5z5A0ycH+9urmnfcjbQMj6ukhzv8fe4-QY8mXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks!
I'll correct the patch ASAP including your modifications.

Le sam. 23 juin 2018 à 19:15, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> a écrit :

>
> Hello lætitia,
>
> My 0.02 € to try to simplify the suggested documentation.
>
> > Check constraint were not
>
> are not
>
> > designed to enforce business rules across tables.
>
> > Avoid using check constraints with function accessing to other tables
>
> accessing other tables (no "to")
>
> > and prefer triggers instead (please refer to <xref linkend="triggers"/>
> > for more information about triggers).
>
> ... and use <xref linkend="triggers"/> instead.
>
> > PostgreSQL won't prevent you from doing so,
>
> Although PostgreSQL ... so,
>
> > but be aware you might encounter difficulties to restore dumps
> > (generated with pg_dump or pg_dumpall) if you do.
>
> beware that dumps generated by <application>pg_*<...> or <...> may be hard
> to restore because of such checks, as the underlying dependencies are not
> taken into account.
>
> --
> Fabien.

--
*Think! Do you really need to print this email ? *
*There is no Planet B.*

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-06-25 14:15:08 Re: Removing obsolete comment block at the top of nbtsort.c.
Previous Message Gaurav Mishra 2018-06-25 13:54:50 Regarding the correct and best way to fetching a tablename in contrib module