Re: strange behavior, hoping for an explanation

From: pasman pasmański <pasman(dot)p(at)gmail(dot)com>
To: Chris Travers <chris(dot)travers(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: strange behavior, hoping for an explanation
Date: 2011-11-11 07:57:46
Message-ID: CAOWY8=ZO9mtAUWfD_8O8ho6T8Ao2cXeXmQS+WrrsODNPQ9CL4A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

See documentation, chapter Viii.E.2.2.2

2011/11/11, Chris Travers <chris(dot)travers(at)gmail(dot)com>:
> Hi;
>
> I have found recently that tables in certain contexts seem to have a
> name pseudocolumn. I was wondering if there is any documentation as
> to what this is and what it signifies.
>
> postgres=# CREATE table TEST2 (a text, b text);
> CREATE TABLE
> postgres=# INSERT INTO test2 values ('aaaa', 'bbbb');
> INSERT 0 1
> postgres=# select t.name FROM test2 t;
> name
> -------------
> (aaaa,bbbb)
> (1 row)
>
> However:
>
>
> postgres=# select name FROM test2 t;
> ERROR: column "name" does not exist
> LINE 1: select name FROM test2 t;
>
> This isn't making any sense to me. Are there certain circumstances
> where a tuple is cast to something like varchar(63)? Does this pose
> pitfals for any columns named 'name' in other contexts?
>
> Best Wishes,
> Chris Travers
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

--
------------
pasman

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2011-11-11 08:43:34 Re: strange behavior, hoping for an explanation
Previous Message Tom Lane 2011-11-11 07:11:20 Re: strange behavior, hoping for an explanation