| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15237: I got "ERROR: source for a multiple-column UPDATE item must be a sub-SELECT or ROW() expression" |
| Date: | 2018-06-14 21:26:33 |
| Message-ID: | CA+TgmobBw7-yQXKD2sx0DiPC=dA_RaZ3f19_ENp4AQcnRcQnzA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Jun 13, 2018 at 12:48 AM, Andrew Gierth
<andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
> The original patch, a self-described "lazy-sunday project", made
> absolutely no mention of any compatibility issue, simply discussed the
> new options it was allowing, and got no feedback or review. Had it
> mentioned or even hinted that existing queries might be broken, I would
> hope that there would have been more discussion at the time.
I think that is a fair criticism.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2018-06-14 22:57:27 | row_to_json(), NULL values, and AS |
| Previous Message | David G. Johnston | 2018-06-14 18:12:37 | Re: BUG #15242: JSON functions not recognizing JSON |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2018-06-14 21:56:05 | Re: [HACKERS] Optional message to user when terminating/cancelling backend |
| Previous Message | Andres Freund | 2018-06-14 20:38:44 | Re: Shared access methods? |