Re: BUG #2204: Feature Req: Unique output column names

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Brandon Black <blblack(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2204: Feature Req: Unique output column names
Date: 2006-01-24 15:52:45
Message-ID: 20060124155245.GI25140@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Brandon Black wrote:

> I realize this is fixable by the user with "AS count_x", this is more an
> issue that came in writing cross-vendor ORM modules in perl, where most
> other database vendors offer some sort of unique naming convention, but
> postgres' output column names are indistinguishable, for the same query.

Use the AS clause, which is the one that actually complies with the SQL
standard. Or show us where the standard mandates name munging and we
will implement it.

--
Alvaro Herrera http://www.advogato.org/person/alvherre
"La fuerza no está en los medios físicos
sino que reside en una voluntad indomable" (Gandhi)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-01-24 16:14:47 Re: BUG #2204: Feature Req: Unique output column names
Previous Message Tom Lane 2006-01-24 15:50:22 Re: BUG #2206: error on declare cursor after a close cursor