| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Clift <justin(at)postgresql(dot)org>, Dave Cramer <dave(at)fastcrypt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: request for sql3 compliance for the update command |
| Date: | 2003-02-20 10:00:14 |
| Message-ID: | 1045735214.1397.8.camel@fuji.krosing.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian kirjutas N, 20.02.2003 kell 06:16:
> Agreed folks are going to have bigger problems from Informix than just
> this, and in fact I used Informix for years and didn't know they allowed
> this.
>
> However, what solution do we have for UPDATE (coll...) = (select val...)
> for folks? It is awkward to repeat a query multiple times in an UPDATE.
>
> I think it makes sense to add it only if it adds functionality.
It makes it easier (less keystrokes) to write as well as similar in
appearance to INSERT, so the same code can be used to generate the
queries.
If we were at adding functionality then IMHO making VALUES(x,y,z) a
proper "rowsource" would be a more worthy effort.
---------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2003-02-20 10:37:34 | Alpha-2 of contrib/tsearch |
| Previous Message | Hannu Krosing | 2003-02-20 09:56:39 | Re: request for sql3 compliance for the update command |