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.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
- Re: Guidance on INSERT RETURNING order Thorsten Glaser
- Re: Guidance on INSERT RETURNING order Federico
- Re: Guidance on INSERT RETURNING order Thorsten Glaser
- Re: Guidance on INSERT RETURNING order Federico
- Re: Guidance on INSERT RETURNING order Thorsten Glaser
- Re: Guidance on INSERT RETURNING order Federico
- Re: Guidance on INSERT RETURNING order John Howroyd
- Re: Guidance on INSERT RETURNING order Mike Bayer
- Re: Guidance on INSERT RETURNING order Rob Sargent
- Re: Guidance on INSERT RETURNING order Federico
- Re: Guidance on INSERT RETURNING order Rob Sargent
- Re: Guidance on INSERT RETURNING order Federico
- Re: Guidance on INSERT RETURNING order Peter J. Holzer
- Re: Guidance on INSERT RETURNING order John Howroyd
- Re: Guidance on INSERT RETURNING order David G. Johnston
- Re: Guidance on INSERT RETURNING order Federico
- Re: Guidance on INSERT RETURNING order David G. Johnston
- Re: Guidance on INSERT RETURNING order Tom Lane
- Re: Guidance on INSERT RETURNING order David G. Johnston
- Re: Guidance on INSERT RETURNING order Federico
- Re: Guidance on INSERT RETURNING order Tom Lane