| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | James Coleman <jtc331(at)gmail(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Insert Documentation - Returning Clause and Order |
| Date: | 2020-12-12 15:11:20 |
| Message-ID: | CAKFQuwbVUBehwAejNrBMwiPDJ61p3Rnjgr42pXkuGrYJ8JRz3A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 12, 2020 at 7:02 AM James Coleman <jtc331(at)gmail(dot)com> wrote:
>
> Certainly almost every ORM, and maybe even other forms of application
> code, need to be able to associate the serial column value returned
> with what it inserted.
>
Yet most ORM would perform single inserts at a time, not in bulk, making
such a feature irrelevant to them.
I don't think having such a feature is all that important personally, but
the question comes every so often and it would be nice to be able to point
at the documentation for a definitive answer - not just one inferred from a
lack of documentation - especially since the observed behavior is that
order is preserved today.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2020-12-12 17:47:59 | Re: pglz compression performance, take two |
| Previous Message | James Coleman | 2020-12-12 14:02:02 | Re: Insert Documentation - Returning Clause and Order |