| From: | Shaozhong SHI <shishaozhong(at)gmail(dot)com> |
|---|---|
| To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL CHECK Constraint |
| Date: | 2021-10-03 18:44:41 |
| Message-ID: | CA+i5Jwb8GmfL_SE7L5YpX6hu5073VJgP89beRrHTFP22O=hh-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
Hi, Kirsten,
That sounds brilliant.
Are there any examples on the web these days?
Regards,
David
On Sunday, 3 October 2021, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> wrote:
> Am Sun, Oct 03, 2021 at 07:16:32PM +0100 schrieb Shaozhong SHI:
>
> > That is interesting. Can errors be captured and saved as data with
> > scripting?
>
> Depends on what the script does.
>
> If the script runs (or is written in) Python the canonical PG
> driver (psycopg2/3) will give you such data.
>
> Karsten
> --
> GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Ramseyer | 2021-10-03 18:47:28 | Re: PostgreSQL CHECK Constraint |
| Previous Message | Karsten Hilbert | 2021-10-03 18:35:01 | Re: PostgreSQL CHECK Constraint |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Ramseyer | 2021-10-03 18:47:28 | Re: PostgreSQL CHECK Constraint |
| Previous Message | Karsten Hilbert | 2021-10-03 18:35:01 | Re: PostgreSQL CHECK Constraint |