On Sunday, October 21, 2012 06:30:14 PM Andrew Dunstan wrote: > On 10/21/2012 12:20 PM, Abhijit Menon-Sen wrote: > > At 2012-10-21 11:49:26 -0400, cbbro...@gmail.com wrote: > >> If there is a natural sequence (e.g. - a value assigned by nextval()), > >> that offers a natural place to apply the usual order-imposing ORDER BY > >> that we are expected to use elsewhere. > > > > Note: "INSERT … RETURNING" doesn't accept an ORDER BY clause. > > No, but you can wrap the INSERT .. RETURNING in a CTE and order that.
Personally I find that a not very practical suggestion. It means you need the ability to sort the data equivalently on the clientside which isn't always easy if you consider platform/locale and whatever differences. Suggesting nextval() doesn't strike me as very practical either because it means that you either need a separate roundtrip to the server to get a bunch of new ids which you then can assign to the to-be-inserted rows or you need the ability to match the returned rows to the inserted rows somehow. Thats not always easy. Andres -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
