From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Andri Möll <andri(at)dot(dot)ee> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Domains, check_violation and undefined column field in error |
Date: | 2015-09-11 12:17:42 |
Message-ID: | CAKFQuwY-qVERCg80qc9oC1DyO2qdYHr2Q0J_9cbthP2aWWteGA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday, September 11, 2015, Andri Möll <andri(at)dot(dot)ee> wrote:
> Hey,
>
> I'm giving DOMAINs a shot and created a simple one with a CHECK on
> PostgreSQL 9.4.4. Sadly, when the check fails, the thrown error (23514,
> check_violation) doesn't seem to contain the column information in the "c"
> field. Should it? Is it just not implemented?
>
> http://www.postgresql.org/docs/9.4/static/errcodes-appendix.html says «As
> of PostgreSQL 9.3, complete coverage for this feature exists only for
> errors in SQLSTATE class 23 (integrity constraint violation), but this is
> likely to be expanded in future.» I believe CHECK violation is in the 23th
> class.
>
> Thanks in advance!
>
> Andri
>
>
An example might help but type input functions do not require nor receive
column information since it is possible to be processing a simple literal
that is not associated with any ore-defined table or view column.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2015-09-11 14:22:12 | Re: clone_schema function |
Previous Message | Andri Möll | 2015-09-11 11:12:53 | Domains, check_violation and undefined column field in error |