| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
| Cc: | Jan Strube <js(at)deriva(dot)de>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: SELECT my_table.varchar FROM my_table |
| Date: | 2010-05-31 15:44:42 |
| Message-ID: | 13743.1275320682@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Richard Broersma <richard(dot)broersma(at)gmail(dot)com> writes:
> On Mon, May 31, 2010 at 7:48 AM, Jan Strube <js(at)deriva(dot)de> wrote:
>> I accidentally encountered a feature in Postgres 8.3 that I couldn't find in
>> the documentation while submitting a query like
>>
>> SELECT my_table.varchar FROM my_table
>>
>> which returns a concatenated string of all field values per row.
>> I wonder where this is documented (and if it has something to do with
>> composite types).
>>
>> Can anyone please explain?
> I don't really know, but the result looks more like a single field
It's equivalent to (my_table.*)::varchar. We've seen enough people
confused by this (or the equivalent cases with text and name as
the target type) that I wonder if we should intentionally break the
symmetry and disable treating this case as a cast. Although I do
rather wonder what the OP expected to happen here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Strube | 2010-05-31 15:59:15 | Re: SELECT my_table.varchar FROM my_table |
| Previous Message | Nilesh Govindarajan | 2010-05-31 15:44:12 | Re: What Linux edition we should chose? |