| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Arturo Guadagnin <tuirutuiru(at)gmail(dot)com>, "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: embedded composite types |
| Date: | 2021-02-20 15:58:21 |
| Message-ID: | 3196308.1613836701@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Saturday, February 20, 2021, Arturo Guadagnin <tuirutuiru(at)gmail(dot)com>
> wrote:
>> I’m just wondering whether this is the expected behaviour or if there is
>> any syntactical magic I’m not aware of ....
> https://www.postgresql.org/docs/current/sql-expressions.html#FIELD-SELECTION
Yeah. Also note that we only recently got around to fixing plpgsql
assignment to allow nested fields; that is
declare p Point2;
...
p.pt1.x = 42;
works in HEAD but not in any released version.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gary Stainburn | 2021-03-17 16:48:45 | select into composite type / return |
| Previous Message | David G. Johnston | 2021-02-20 15:07:49 | Re: embedded composite types |