| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | <mike(at)aubit(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Hannu Krosing" <hannu(at)tm(dot)ee> |
| Cc: | "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-21 08:10:00 |
| Message-ID: | 03AF4E498C591348A42FC93DEA9661B8259C97@mail.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Mike Aubury [mailto:mike(at)aubit(dot)com]
> Sent: 20 February 2003 19:10
> To: Dave Page; Tom Lane; Hannu Krosing
> Cc: Dave Cramer; Peter Eisentraut; Pgsql Hackers
> Subject: Re: [HACKERS] request for sql3 compliance for the
> update command
>
>
> Informix supports 2 different styles for the update - your
> one would have to
> be written :
>
>
> UPDATE djp SET(col1, col2) = ((SELECT col1,col2 FROM
> some_other_table))
>
> Notice the double brackets !
> The first signifies a list of values - the second is the
> brackets around the
> subquery...
>
> (NB If you try to reference the same table in the Update -
> you'll get an
> error....)
Ahh, of course. I tried double brackets 'cos I figured I might need one
pair to indicate the set and one to indicate the subselect, but I didn't
think to try a different table.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-02-21 08:10:13 | Loss of cluster status |
| Previous Message | Christopher Kings-Lynne | 2003-02-21 07:23:50 | Re: [PATCHES] Non-colliding auto generated names |