| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Insert Documentation - Returning Clause and Order |
| Date: | 2020-12-10 13:31:28 |
| Message-ID: | CAExHW5u-Xj_pPzdbwuJAReXbxobTB6iTYZMX+HBZmBWexBjk4A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 9, 2020 at 9:10 PM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> Hey,
>
> Would it be accurate to add the following sentence to the INSERT documentation under "Outputs"?
>
> "...inserted or updated by the command." For a multiple-values insertion, the order of output rows will match the order that rows are presented in the values or query clause.
Postgres's current implementation may be doing so, but I don't think
that can be guaranteed in possible implementations. I don't think
restricting choice of implementation to guarantee that is a good idea
either.
--
Best Wishes,
Ashutosh Bapat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2020-12-10 13:43:33 | OpenSSL connection setup debug callback issue |
| Previous Message | Konstantin Knizhnik | 2020-12-10 13:03:14 | Re: On login trigger: take three |