Re: Policy on schema-qualified names

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joachim Wieland <joe(at)mcknight(dot)de>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Policy on schema-qualified names
Date: 2006-01-31 18:46:42
Message-ID: 5533.1138733202@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joachim Wieland <joe(at)mcknight(dot)de> writes:
> Making assumptions on the length of an error message seems to be moot
> anyway, since you don't know the length of the names of user defined objects
> in advance, nor do you know the length of the translated message strings in
> different languages.

It's certainly all pretty fuzzy, but adding an additional name to an
error message has to be seen as a significant increase in the message
length. The worst cases are for things like foreign-key messages, where
you'd be putting *two* additional identifiers into the message.

I think the precision argument is misguided. The direction that we
ought to be going in is to add separate fields to error reports that
contain just the names of the relevant objects (without any other
decoration). This is needed anyway to allow client-side programs to
extract the information without having to parse human-readable text
messages ... and IIRC it's required by some part of the SQL spec, too.
I imagine such fields wouldn't be shown at default verbosity, but you
could look at them if you needed to find out which schema a referenced
object belonged to.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-01-31 18:57:52 Re: New project launched : PostgreSQL GUI Installer for
Previous Message Joachim Wieland 2006-01-31 18:29:36 Re: Policy on schema-qualified names