From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Cramer <dave(at)fastcrypt(dot)com>, Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: request for sql3 compliance for the update command |
Date: | 2003-02-20 05:24:45 |
Message-ID: | 200302200524.h1K5OjJ25810@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-02-20 06:13:43 | deleting dependencies |
Previous Message | Christopher Kings-Lynne | 2003-02-20 04:54:27 | Re: request for sql3 compliance for the update command |