| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | scott(dot)comer(at)voya(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: return type marked optional but isn't |
| Date: | 2024-02-21 17:33:23 |
| Message-ID: | CAKFQuwZ03akGQrj2E3yTaUc3k60QB4_H2fUEYFqX5UhdN7hCrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Feb 21, 2024 at 10:10 AM 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/13/sql-createfunction.html
> Description:
>
> the documentation for creating a function shows [ RETURNS rettype | RETURNS
> TABLE ( column_name column_type [, ...] ) ] but returns is not optional. At
> least when specifying LANGUAGE plpgsql. All the online advice suggests
> specifying RETURNS void as the solution.
>
As with most conditionally option things in the docs reading the
description for the item tells you when it can be omitted.
rettype: "When there are OUT or INOUT parameters, the RETURNS clause can be
omitted."
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Wienhold | 2024-02-21 22:16:13 | Re: [PATCH] Fix link to pg_ident_file_mappings |
| Previous Message | PG Doc comments form | 2024-02-21 16:54:48 | return type marked optional but isn't |