| From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Mailing Lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows |
| Date: | 2012-10-21 15:49:26 |
| Message-ID: | CAFNqd5XkSCoeX-146AFAqdYZ=0P-bo1YrRbFtrC=00ywn_JEnQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I agree that it seems inappropriate to preserve order. That seems an
inappropriate imposition, inconsistent with what SQL does elsewhere.
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.
I suppose it is troublesome if there is no such natural sequence, but I
wouldn't think it too meaningful to expect order without some visible
source of order.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-10-21 15:59:30 | Re: No, pg_size_pretty(numeric) was not such a hot idea |
| Previous Message | David Johnston | 2012-10-21 15:05:17 | Re: Re: [PATCH] Enforce that INSERT...RETURNING preserves the order of multi rows |