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

From Christopher Kings-Lynne
Subject Re: request for sql3 compliance for the update command
Date
Msg-id 066a01c2d89c$25d8d3e0$6500a8c0@fhp.internal
Whole thread Raw
In response to Re: request for sql3 compliance for the update command  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: request for sql3 compliance for the update command  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> 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?

Chris




pgsql-hackers by date:

Previous
From: Gavin Sherry
Date:
Subject: Re: request for sql3 compliance for the update command
Next
From: Bruce Momjian
Date:
Subject: Re: request for sql3 compliance for the update command