| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robins Tharakan <tharakan(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Per row status during INSERT .. ON CONFLICT UPDATE? |
| Date: | 2015-05-19 17:54:31 |
| Message-ID: | CAM3SWZRBdCkP5Dm8-5mTd3axRx=XWUDVT8WmgA2KB3-ZcoKK7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 19, 2015 at 10:49 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> The RETURNING clause just allows us to return columns, but am unable to
>> find a way to know 'what' happened to a given row.
>
> There previously has been discussion about extending RETURNING to allow
> to return the before/after row. But to me that's a mostly independent
> feature to ON CONFLICT.
That's certainly something we talked about. It could probably be done
with some kind of magical expression. I have to wonder how many of the
people that are sure that they need this really do, though. Is it
really natural to care about this distinction with idiomatic usage?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-05-19 18:02:15 | Re: a few thoughts on the schedule |
| Previous Message | Andres Freund | 2015-05-19 17:49:29 | Re: Per row status during INSERT .. ON CONFLICT UPDATE? |