From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | code(at)lhorn(dot)de |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: error on „ 38.5. Query Language (SQL) Functions“: a single row is returned |
Date: | 2022-09-18 15:01:04 |
Message-ID: | 157902.1663513264@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
PG Doc comments form <noreply(at)postgresql(dot)org> writes:
> The following documentation comment has been logged on the website:
> Page: https://www.postgresql.org/docs/14/xfunc-sql.html
> Description:
> On the page „ 38.5. Query Language (SQL) Functions“ below the example
> CREATE FUNCTION new_emp() RETURNS emp AS $$
> SELECT ROW('None', 1000.0, 25, '(2,2)')::emp;
> $$ LANGUAGE SQL;
> this sentence is wrong:
> „ Here we wrote a SELECT that returns just a single column of the correct
> composite type.“
> It is not a single column but a single row that is returned.
It's also a single column, which is more relevant to the point being
made. Compare this to the immediately preceding example.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Westermann (DWE) | 2022-09-20 12:24:08 | Are we really using 23 bytes on most machines? |
Previous Message | PG Doc comments form | 2022-09-18 08:44:37 | error on „ 38.5. Query Language (SQL) Functions“: a single row is returned |