pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: llucenic@gmail.com
Subject: CHECK constraints - order of evaluation
Date: Thu, 14 May 2020 09:06:34 +0000
Message-ID: <158944719436.678.10650510391656422908@wrigleys.postgresql.org> (raw)

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/9.6/ddl-constraints.html
Description:

I think the information about the "order of execution" when checking CHECK
constraints when inserting or updating records is missing in the
documentation.
There seems to be an old e-mail thread on the topic, however, there is no
information on whether the patch submitted was already merged and if so, in
which version of PostgreSQL.
I also suggest it would be good to point out in the documentation how the
order of CHECK constraints is created when there are more column CHECK
constraints and table CHECK constraints (i.e. in mixed cases) or whether
only the name of the constraint is relevant when it comes to it, not its
type (column/table).

Thank you very much in advance.
Kindest regards,
Ľudovít


view thread (2+ messages)  latest in thread

Message-ID: <158944719436.678.10650510391656422908@wrigleys.postgresql.org>
Permalink:  ../158944719436.678.10650510391656422908@wrigleys.postgresql.org/
Also on:    postgresql.org/message-id/158944719436.678.10650510391656422908@wrigleys.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, llucenic@gmail.com
  Subject: Re: CHECK constraints - order of evaluation
  In-Reply-To: <158944719436.678.10650510391656422908@wrigleys.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox