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

From: Ian Barwick <barwick(at)gmail(dot)com>
To: adrian(dot)klaver(at)gmail(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Unexpected result from selecting an aliased but non-existing column called "name"
Date: 2010-03-17 14:11:40
Message-ID: 1d581afe1003170711l42416d5di421a77fc3ed52576@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Adrian,

2010/3/9 Adrian Klaver <adrian(dot)klaver(at)gmail(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chokshi, Meghaben 2010-03-17 14:28:21 DBT-2 Error
Previous Message Albe Laurenz 2010-03-17 14:06:20 pgreplay log file replayer released