Re: Unexpected result from selecting an aliased but non-existing column called "name" - Mailing list pgsql-general

From Ian Barwick
Subject Re: Unexpected result from selecting an aliased but non-existing column called "name"
Date
Msg-id 1d581afe1003170711l42416d5di421a77fc3ed52576@mail.gmail.com
Whole thread Raw
In response to Re: Unexpected result from selecting an aliased but non-existing column called "name"  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-general
Hi Adrian,

2010/3/9 Adrian Klaver <adrian.klaver@gmail.com>:
> On Tuesday 09 March 2010 12:50:45 am Ian Barwick wrote:
>> Hi
>>
>> I was wondering where some spurious information in a query was
>> coming from - it looked like something was inserting all the
>> values of a table row as a comma-separated list.
>>
>> It turns out I was attempting to reference a non-existent column
>> called (literally) "name", which instead of throwing an error produces
>> the aforementioned list. This only seems to happen with "name", and
>> only if it is referenced with the table name or alias.
>>
>> Ian Barwick
>
> See this recent thread for explanation:
> http://archives.postgresql.org/pgsql-general/2010-02/msg01038.php

Thanks for the info, apologies for the delay in replying.

Certainly explains what's going on, though it seems a bit of a "gotcha".


Regards

Ian Barwick

pgsql-general by date:

Previous
From: Vick Khera
Date:
Subject: Re: app table names
Next
From: "Chokshi, Meghaben"
Date:
Subject: DBT-2 Error