Re: [PATCHES] extension for sql update - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [PATCHES] extension for sql update
Date
Msg-id 200607271328.k6RDS5519882@momjian.us
Whole thread Raw
In response to Re: [PATCHES] extension for sql update  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] extension for sql update
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Tom Lane wrote:
> >> UPDATE mytab SET (foo, bar, baz) =
> >> (SELECT alpha, beta, gamma FROM othertab WHERE key = mytab.key);
>
> > That UPDATE example is interesting because I remember when using
> > Informix that I had to do a separate SELECT statement for each UPDATE
> > column I wanted to update.  I didn't realize that you could group
> > columns and assign them from a single select --- clearly that is a
> > powerful syntax we should support some day.
>
> No question.  The decision at hand is whether we want to look like
> we support it, when we don't yet.  I'd vote not, because I think the
> main use-case for the row-on-the-left syntax is exactly this, and
> so I fear people will just get frustrated if they see it in the
> syntax synopsis and try to use it.

Agreed.  My guess is that a soluion that allows SELECT to return
multiple values is going to be in another area of the code, and will
require us to remove this code once that is done.

--
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] extension for sql update
Next
From: Joshua Reich
Date:
Subject: Re: [COMMITTERS] pgsql: /contrib/cube improvements: Update