From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Raymond Brinzer <ray(dot)brinzer(at)gmail(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Records, Types, and Arrays |
Date: | 2023-05-19 12:23:19 |
Message-ID: | CAKFQuwYA-Q0rOS5d8RWM0t-kpTiE4Ka7KmF0OUBfWxeGD=N81g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
The convention here is to inline or, at worse, bottom post, trimming
irrelevant context.
On Friday, May 19, 2023, Raymond Brinzer <ray(dot)brinzer(at)gmail(dot)com> wrote:
>
> I'm guessing that row() isn't really a function, then? And even so,
> assuming this is the important difference, how is the ability to change row
> structure on the fly making the cast possible? In what way would the query
> calling get_row() be critical?
>
Row() is pure syntax. It distinguishes (col) vs. row(col) where the first
is just a column in parentheses and the second is a composite with one
column member.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Mueller | 2023-05-19 14:25:43 | Re: a simple-minded question about updating |
Previous Message | sujay kadam | 2023-05-19 11:47:47 | How to connect with PostgreSQL Database with SSL using Certificates and Key from client Eclipse in Java |