From: | Federico <cfederico87(at)gmail(dot)com> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Guidance on INSERT RETURNING order |
Date: | 2023-04-11 22:02:34 |
Message-ID: | CAN19dydJ9rC4aNx1KENpF3Zne9gYAtA=z3BhV8bdnbOJs45DRg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 11 Apr 2023 at 23:46, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
>
>
> >> Can your client retain a hashmap of md5,data pairings, allowing the
> >> lookup on the way back using the returned data and supplied id?
> >>
> > When using unique columns or similar, that's something that is done,
> > but if there are no unique columns in the value no match can be done
> > reliably with the source data, since sqlalchemy is a library that
> > allows arbitrary schemas to be generated.
> >
> > Thanks for the reply,
> > Federico
> So you're returned data is not what was sent to the server? Otherwise it
> should generate the same md5, as I understand it. Identical data would
> of course be a problem.
>
That should be the case, yes.
If a table has a non-nullable unique key, it should be possible to use
a hashmap and perform that lockup. We are planning on implementing
something like this to cover the cases where it can be used.
Thanks for the reply,
Federico
From | Date | Subject | |
---|---|---|---|
Next Message | Thorsten Glaser | 2023-04-11 22:20:56 | Re: Guidance on INSERT RETURNING order |
Previous Message | Federico | 2023-04-11 21:55:28 | Re: Guidance on INSERT RETURNING order |