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

From Gregory Stark
Subject Re: Better error message for select_common_type()
Date
Msg-id 87ve3kan4g.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Better error message for select_common_type()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Better error message for select_common_type()
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Or we could apply Peter's patch more or less as-is, but I don't like
> that.  I don't think it solves the stated problem: if you know that CASE
> branches 3 and 5 don't match, that still doesn't help you in a monster
> query with lots of CASEs.  I think we can and must do better.

Do we have something more helpful than "branches 3 and 5"? Perhaps printing
the actual transformed expressions?


--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about
EnterpriseDB'sPostgreSQL training!
 


pgsql-hackers by date:

Previous
From: 张 海 泉
Date:
Subject: 业务合办 !
Next
From: Alvaro Herrera
Date:
Subject: Re: [something I can't read]