Re: Constraint documentation
От | Lætitia Avrot |
---|---|
Тема | Re: Constraint documentation |
Дата | |
Msg-id | CAB_COdiKFs=HbKmrdHVK1sbKy=8GYKaa1WPN8o1GjuzAZnOT_A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Constraint documentation (Lætitia Avrot <laetitia.avrot@gmail.com>) |
Ответы |
Re: Constraint documentation
|
Список | pgsql-hackers |
Hello,
Ok, I corrected the patch as suggested. I hope I did it right.Le lun. 25 juin 2018 à 16:02, Lætitia Avrot <laetitia.avrot@gmail.com> a écrit :
Thanks!I'll correct the patch ASAP including your modifications.Le sam. 23 juin 2018 à 19:15, Fabien COELHO <coelho@cri.ensmp.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.
--
Think! Do you really need to print this email ?
There is no Planet B.
There is no Planet B.
Вложения
В списке pgsql-hackers по дате отправления: