| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UPDATE ... SET (a, b, c) = (expr) |
| Date: | 2009-08-21 15:03:56 |
| Message-ID: | 4087.1250867036@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> So is this the right way to approach the problem, or am I missing some
> simpler way?
See discussions of NikhilS's patch last year. I think the conclusion we
had arrived at was that we should refactor the representation of SubLink
so that a single-row subselect could be responsible for producing the
values of more than one Param (located in more than one place in the
query's expression trees). Otherwise you get into having to redefine
the representation of targetlists, which will break more code than is
pleasant to think about.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel Pouré | 2009-08-21 16:22:41 | Feedback about Drupal SQL debugging |
| Previous Message | Tom Lane | 2009-08-21 14:41:06 | Re: Geometric Elimination |