Re: BUG #16158: Check constraints using SQL functions work incorrectly
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: pjander2@gmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2019-12-10T15:00:24Z
Lists: pgsql-bugs
On Tue, Dec 10, 2019 at 5:28 AM PG Bug reporting form < noreply@postgresql.org> wrote: > The following bug has been logged on the website: > > Bug reference: 16158 > Logged by: Piotr Jander > Email address: pjander2@gmail.com > PostgreSQL version: 11.5 > Operating system: x86_64 GNU/Linux > Description: > > [...] > > My conjecture is that the bug is due to the use of SQL functions in the > check. > However, the > [docs](https://www.postgresql.org/docs/9.4/ddl-constraints.html) > on constraints do not mention any limitations on using such SQL functions > in > checks. If such limitations exist, they should be mentioned in the docs. > You should read the most current version of the documentation for a feature before reporting a bug. In this case the warnings you desired have been added to more recently versions of the documentation. https://www.postgresql.org/docs/12/ddl-constraints.html Short answer, check constraints are designed to work only with data present on the table upon which they are defined. Use triggers to work with other tables. David J.
Commits
-
Doc: back-patch documentation about limitations of CHECK constraints.
- af4006f0097a 10.12 landed
- 7ef59c9b1839 9.6.17 landed
- 6bf23e8c6e06 9.5.21 landed
- 49b83f647434 11.7 landed
- 3ddd8ee7167f 9.4.26 landed