Re: Dyamic updates of NEW with pl/pgsql

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, depesz(at)depesz(dot)com, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, strk(at)keybit(dot)net
Subject: Re: Dyamic updates of NEW with pl/pgsql
Date: 2010-03-12 12:32:27
Message-ID: b42b73151003120432j730c4cber502c6abfcf8fb6fb@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 11, 2010 at 11:24 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Merlin Moncure escribió:
>
>
>> (small aside: the other biggie would be able to push a composite type
>> in to an update statement...something like 'update foo set foo =
>> new').  This is really great...some variant of this question is
>> continually asked it seems.
>
> Can't you already do that with EXECUTE ... USING NEW?  hmm, ah, but you
> have to specify the columns in NEW, so it doesn't really work for you,
> does it?

right...with inserts you can expand the composite type without listing
the columns. updates can't do it because of syntax issues, even if
you go dynamic.

merlin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2010-03-12 14:32:19 Re: invalid UTF-8 via pl/perl
Previous Message Magnus Hagander 2010-03-12 11:13:43 Re: walreceiver is uninterruptible on win32