Re: NOT NULL violation and error-message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: Andreas Joseph Krogh <andreak(at)officenet(dot)no>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: NOT NULL violation and error-message
Date: 2010-01-12 14:25:59
Message-ID: 3191.1263306359@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> writes:
> Do we have any guideline about the message for identifier names?

The issue has come up before. I think that what we really need here is
to implement additional fields in error message reports, so that the
name and schema name of the relevant object can be pulled out of the
message by programs without having to parse the message text. If we had
that, it would reduce the pressure to clutter the basic message text
this way. It would also improve our compliance with the SQL standard,
which says you're supposed to do it like that.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-01-12 14:35:29 Re: pg_dump sort order for functions
Previous Message Boszormenyi Zoltan 2010-01-12 14:23:19 Re: [PATCH] Provide rowcount for utility SELECTs