Re: Constraint documentation
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Lætitia Avrot <laetitia.avrot@gmail.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2018-06-23T17:15:35Z
Lists: pgsql-hackers
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.
Commits
-
Clarify that cross-row constraints are unsupported
- 36d442a25a1a 12.0 landed