Re: request for sql3 compliance for the update command - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: request for sql3 compliance for the update command
Date
Msg-id 200302200524.h1K5OjJ25810@candle.pha.pa.us
Whole thread Raw
In response to Re: request for sql3 compliance for the update command  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-hackers
Christopher Kings-Lynne wrote:
> 
> > BTW, looking at the SQL99 standard, I see that you can do
> > 
> > UPDATE table SET ROW = foo WHERE ...
> > 
> > where foo is supposed to yield a row of the same rowtype as table
> > --- I didn't dig through the spec in detail, but I imagine foo can
> > be a sub-select.  I don't care a whole lot for that, though, since it
> > would be a real pain in the neck if you're not updating all the columns.
> > You'd have to go
> > 
> > UPDATE table SET ROW = (SELECT table.a, table.b, foo.x, ... FROM foo)
> 
> How is the Informix syntax any better?

With Informix, you specify the columns you want updated in parens,
rather than saying ROW.  Does the spec allow a list of columns after
ROW?  That would be nice, like Informix.  I doubt many folks update all
the columns.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: request for sql3 compliance for the update command
Next
From: "Christopher Kings-Lynne"
Date:
Subject: deleting dependencies