Re: Domain Constraint Violation Error Messages

On Wed, Jul 25, 2018 at 9:19 AM, Benjamin Coutu <ben(dot)coutu(at)zeyos(dot)com> wrote:

> > No way. PG11 has been feature frozen for quite a while.
>
> I understand, thanks. I thought, maybe it would qualify as a trivial "bug"
> fix, sorry for that.
> Would it be hard to also include column name(s) for PG 12 then?
>

IIUC this general problem (it also applies to, e.g., varchar(20)) ​is well
known and has been discussed many times, as recently as the last 6 months
if memory serves. The lack of concrete progress, as well as general
sentiment, leads me to think that the cost-benefit calculation for
improving things in this area is extremely poor. It is not an easy (and,
likely inexpensive run-time effort) thing to add context to what is a
simple type input function error.

David J.

P.S. I'm not sure of the specifics off the top of my head but the inclusion
of "NOT NULL" on the domain has limits. I believe the recommended setup is
to also include NOT NULL on the relevant table definitions.