From: | Christian Ramseyer <ramseyer(at)netnea(dot)com> |
---|---|
To: | Shaozhong SHI <shishaozhong(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL CHECK Constraint |
Date: | 2021-10-03 18:47:28 |
Message-ID: | dd474d68-b873-e5c3-eedb-511c90ed2913@netnea.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
> The reported error looks like this:
>
> postgres(at)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
From | Date | Subject | |
---|---|---|---|
Next Message | Shaozhong SHI | 2021-10-03 18:53:51 | Re: PostgreSQL CHECK Constraint |
Previous Message | Shaozhong SHI | 2021-10-03 18:44:41 | Re: PostgreSQL CHECK Constraint |
From | Date | Subject | |
---|---|---|---|
Next Message | Shaozhong SHI | 2021-10-03 18:53:51 | Re: PostgreSQL CHECK Constraint |
Previous Message | Shaozhong SHI | 2021-10-03 18:44:41 | Re: PostgreSQL CHECK Constraint |