| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "jonathan(at)allard(dot)io" <jonathan(at)allard(dot)io>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: json_populate_record |
| Date: | 2020-08-13 23:08:41 |
| Message-ID: | CAKFQuwbx6vZAh7zZOmW5ZGVbnWutkLHedns3tdwho9KUiJdOCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thursday, August 13, 2020, PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/functions-json.html
> Description:
>
> It is not clear what the parameter `base` means
>
I agree there is room for improvement here. The referenced note does’t use
the term “base” which making finding the correct note among the various
possibilities more difficult. The example seems sufficiently illustrative
though. Those functions convert json to SQL composite types. You need to
pass in which composite type to convert to. That is the “base” type. One
normally does this by casting SQL null to the desired composite type;
usually one associated with an existing table.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-08-14 00:39:06 | Re: json_populate_record |
| Previous Message | PG Doc comments form | 2020-08-13 22:17:56 | json_populate_record |