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

From Alvaro Herrera
Subject Re: Better error message for select_common_type()
Date
Msg-id 20070423233311.GH12624@alvh.no-ip.org
Whole thread Raw
In response to Re: Better error message for select_common_type()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

> For the VALUES case, the suggestion of "row" and "column" terminology
> seems the right thing, but for UNION it would be better to use "branch"
> perhaps ("row" certainly seems misleading).  How can we make that work
> without indulging in untranslatable keyword-insertion?
> 
> Another possibility is "alternative" and "column", which seems like it
> applies more or less equally poorly to both cases.

Maybe it would be good to have distinctive terminology if at all
possible, as it will be clearer for both cases.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Better error message for select_common_type()
Next
From: "Gustavo Tonini"
Date:
Subject: Re: Fragmentation project