> > > That seems very reasonable; if the situation is similar on PostgreSQL, > > > then I'd suggest making that very clear in the INSERT[2] and UPDATE[3] docs. > > > > There is clearly no mention of such a guarantee in our documentation. > > Yes, which is just how SQL works: a set doesn't have any ordering unless an > explicit one has been defined, RETURNING is no exception to that.
Thanks for confirming that such a guarantee doesn't exist. I would still suggest explicitly calling that out in the docs around RETURNING, since that seems like an understand pitfall; personally-speaking, this certainly wasn't clear to me when first looking at it (even if it is now).
