Re: [PATCHES] extension for sql update

Поиск
Список
Период
Сортировка
Искать
От
Rod Taylor
Тема
Re: [PATCHES] extension for sql update
Дата
Msg-id
1154362102.24186.394.camel@home
Ответ на
Список
Дерево обсуждения
Re: [PATCHES] extension for sql update Susanne Ebrecht <miracee@miracee.de>
Re: [PATCHES] extension for sql update Tom Lane <tgl@sss.pgh.pa.us>
Re: [PATCHES] extension for sql update Susanne Ebrecht <miracee@miracee.de>
Re: [PATCHES] extension for sql update "Florian G. Pflug" <fgp@phlo.org>
Re: [PATCHES] extension for sql update Jim Nasby <jnasby@pervasive.com>
Re: [PATCHES] extension for sql update Bruce Momjian <bruce@momjian.us>
On Mon, 2006-07-31 at 17:26 +0200, Peter Eisentraut wrote:
> Am Mittwoch, 26. Juli 2006 22:58 schrieb Tom Lane:
> > The reason people want this syntax is that they expect to be
> > able to write, say,
> >
> > 	UPDATE mytab SET (foo, bar, baz) =
> > 	    (SELECT alpha, beta, gamma FROM othertab WHERE key = mytab.key);
> 
> I don't find any derivation in the standard that would permit this.  The only 
> thing I could find are variations on
> 
> SET (a) = x  -- no parentheses
> SET (a, b) = (x, y)
> SET (a, b) = ROW (x, y)
> 
> where x and y are some sort of value expression.  I would have expected the 
> sort of thing that you describe, but if you know how to derive that, I'd like 
> to see it.

I believe  can be
one or more  which includes a .
 gives us the  option.

For that matter the below portion of  gives us: |  
    

This breaks down into one or more comma separated s.

UPDATE tab SET (...) = ((SELECT foo, bar from a), (select bif,baz from
b));

-- 


В списке pgsql-hackers по дате отправления
От: Andrew Dunstan
Дата:
От: Michael Fuhr
Дата:
FAQ