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

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

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

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2010-03-09 14:26:35 Re: Urgent help needed- alias name in update statement
Previous Message Steve T 2010-03-09 14:03:47 Re: Urgent help needed- alias name in update statement