Re: BUG #14616: error message without schema

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ódor Balázs <balazs(at)obiserver(dot)hu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14616: error message without schema
Date: 2017-04-10 17:09:49
Message-ID: 16289.1491844189@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?UTF-8?B?w5Nkb3IgQmFsw6F6cw==?= <balazs(at)obiserver(dot)hu> writes:
> db=# create schema test;
> CREATE SCHEMA
> db=# create domain test.testdomain as varchar(200);
> CREATE DOMAIN
> db=# create table test.testtable (col test.testdomain);
> CREATE TABLE
> db=# insert into test.testtable (col) values ('test text');
> INSERT 0 1
> db=# alter domain test.testdomain add constraint testdomain_check check
> (value ~ 'a.+');
> ERROR: column "col" of table "testtable" contains values that violate
> the new constraint

The data you're after *is* available in the extended fields of that error:

db=# \errverbose
ERROR: 23514: column "col" of table "testtable" contains values that violate the new constraint
SCHEMA NAME: test
TABLE NAME: testtable
COLUMN NAME: col
LOCATION: validateDomainConstraint, typecmds.c:2750

We've had multiple conversations about whether to include objects' schema
names in the primary error message text, and so far the answer continues
to be "no". There seem to be more people who would find it to be clutter
than would find it to be useful. Certainly it wouldn't make sense to
change that style decision for just this one message.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ódor Balázs 2017-04-10 17:19:37 Re: BUG #14616: error message without schema
Previous Message Ódor Balázs 2017-04-10 16:58:43 Re: BUG #14616: error message without schema