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: | James Coleman <jtc331(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-14 14:09:36 |
Message-ID: | CAExHW5t-qErdoEnrO5N3=UwYN16NjKn0VG0M7M7pXZfyobv_iQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Dec 12, 2020 at 8:41 PM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> 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.
>
That's a valid usecase, but adding such a guarantee in documentation
would restrict implementation. So at best we can say "no order is
guaranteed". But we write what's guaranteed. Anything not written in
the documents is not guaranteed.
There are ways to get it working, but let's not go into those details
in this thread.
--
Best Wishes,
Ashutosh Bapat
From | Date | Subject | |
---|---|---|---|
Next Message | Amul Sul | 2020-12-14 14:33:32 | Re: [Patch] ALTER SYSTEM READ ONLY |
Previous Message | Fujii Masao | 2020-12-14 14:01:52 | Re: Feature improvement for pg_stat_statements |