Re: [PATCHES] extension for sql update

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Susanne Ebrecht <miracee(at)miracee(dot)de>
Subject: Re: [PATCHES] extension for sql update
Date: 2006-08-11 22:11:03
Message-ID: 20060811221103.GZ27928@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Fri, Aug 11, 2006 at 10:59:45AM -0400, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Bruce Momjian wrote:
> > > Are we sure we don't want the patch for a non-subquery version of SET
> > > ROW for 8.2?
> > >
> > > o Allow UPDATE tab SET ROW (col, ...) = (...) for updating
> > > multiple columns
> >
> > It seems to be moderately useful as a notational convenience for now.
> >
> > Is it too hard to rip it back out once the full row support arrives?
> > That seems speculation at best anyway.
>
> That's what I was thinking. Glad someone else replied. ;-)

If you're looking for votes, +1. I'll gladly take a subset of the SQL
standard UPDATE table SET (...) = (...) over having nothing.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Hammond 2006-08-11 22:57:42 perl namespace for postgres specific modules?
Previous Message Alvaro Herrera 2006-08-11 21:27:46 Re: 8.2 features status

Browse pgsql-patches by date

  From Date Subject
Next Message Heikki Linnakangas 2006-08-11 23:16:58 Re: [HACKERS] Maintaining cluster order on insert
Previous Message Jim Nasby 2006-08-11 21:02:25 Re: [HACKERS] Forcing current WAL file to be archived