Re: Better error message for select_common_type() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Better error message for select_common_type()
Date
Msg-id 14018.1177365182@sss.pgh.pa.us
Whole thread Raw
In response to Better error message for select_common_type()  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Better error message for select_common_type()  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: RETURN QUERY in PL/PgSQL?
Next
From: Tom Lane
Date:
Subject: Re: Wild idea: 9.0?