Re: Better error message for select_common_type()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Better error message for select_common_type()
Date: 2007-04-23 21:53:02
Message-ID: 14018.1177365182@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> None of this will help if you have multiple unrelated clauses that
> invoke select_common_type(), but that might be better handled using the
> parser location mechanism.

+1 on using the parser location mechanism and avoiding the terminology
problem altogether. I fear though that we're not set up to have
multiple locations in one error report. Will it be sufficient if we
point at one of the two offending expressions? (I'd guess pointing at
the second makes the most sense, if feasible.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lukas Kahwe Smith 2007-04-23 21:53:08 Re: Wild idea: 9.0?
Previous Message Tom Lane 2007-04-23 21:48:57 Re: RETURN QUERY in PL/PgSQL?