Re: row constructors - Mailing list pgsql-general

From Rory Campbell-Lange
Subject Re: row constructors
Date
Msg-id 20090212163833.GC14801@campbell-lange.net
Whole thread Raw
In response to Re: row constructors  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: row constructors
List pgsql-general
On 12/02/09, Merlin Moncure (mmoncure@gmail.com) wrote:
> On Thu, Feb 12, 2009 at 5:03 AM, Sim Zacks <sim@compulab.co.il> wrote:
> > Never mind. I found an old post.
> > I just needed to do:
> > insert into a1 select (f2).* from a2;
> >
> > I didn't find it the first time I searched because I was looking for row
> > constructors, and the post I found used the term composite value.
>
> I'm scheming to get that fixed.  The main reason is that while the
> insert workaround works, there is no similar workaround for 'update'.

Do you mean that the currently unsupported behaviour

  UPDATE accounts SET (contact_last_name, contact_first_name) =
    (SELECT last_name, first_name FROM salesmen
     WHERE salesmen.id = accounts.sales_id);

will be fixed? (with reference to http://www.postgresql.org/docs/8.3/static/sql-update.html#AEN61082)

Rory

pgsql-general by date:

Previous
From: Rory Campbell-Lange
Date:
Subject: Re: Update table with random values from another table
Next
From: Steve Crawford
Date:
Subject: Re: Killing OIDs