Subject: Re: PostgreSQL CHECK Constraint
To: Shaozhong SHI <shishaozhong@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
References: 
 <CA+i5JwYC26KFQjXYBk-gNYxofhkjnWQBB-+goeusMajVdv_2_w@mail.gmail.com>
 <CA+i5Jwbo7QL+H4Q1tFV1CUQaa4ZzTLZFVwEC-YKe-bDVRsOBMA@mail.gmail.com>
 <42aaef2a-6f55-0449-5a35-d6507d333af1@netnea.com>
 <CA+i5JwbQR7kYG02LuNxfsyCcGH9YkMhdYKJ3fx78LorU-CyzLA@mail.gmail.com>
From: Christian Ramseyer <ramseyer@netnea.com>
Message-ID: <dd474d68-b873-e5c3-eedb-511c90ed2913@netnea.com>
Date: Sun, 3 Oct 2021 20:47:28 +0200
MIME-Version: 1.0
In-Reply-To: 
 <CA+i5JwbQR7kYG02LuNxfsyCcGH9YkMhdYKJ3fx78LorU-CyzLA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/dd474d68-b873-e5c3-eedb-511c90ed2913%40netnea.com>
Precedence: bulk

>     The reported error looks like this:
>
>     postgres@dellstore ERROR:  new row for relation "test_customers"
>     violates check constraint "check_age"
..
>
>     This errors appears in the serverlog which has many format and
>     forwarding options, you can read about them here:

On 03.10.21 20:16, Shaozhong SHI wrote:
> Hi， Christian,
> That is interesting.  Can errors be captured and saved as data with
> scripting?

Yes that works quite the same, e.g. in Python you can do

try:
    cur.execute("insert into test_customers (firstname, lastname, age)
            values ( %s, %s, %s)", ("Bobby", "Tables", 10))
except psycopg2.errors.CheckViolation as e:
    print(f"That didn't work: {e.cursor.query} failed")
    print(f"{e.pgerror}")


HTH