| From: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Susanne Ebrecht <miracee(at)miracee(dot)de>, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] extension for sql update |
| Date: | 2006-07-27 15:42:19 |
| Message-ID: | 44C8DEDB.9080408@phlo.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Susanne Ebrecht <miracee(at)miracee(dot)de> writes:
>> ... We could provide the mixed update syntax and leave the
>> typed row value expression for the next release. Do you agree?
>
> I don't really see the point --- the patch won't provide any new
> functionality in anything like its current form, because you can
> always just write the separate expressions in the simple one to
> one way. If we do offer the row-on-the-left syntax then people
> will try to put sub-selects on the right, and won't get anything
> beyond an unhelpful "syntax error" message. So my vote would be
> to leave it alone until we have a more complete implementation.
It has the advantage that inserts and updates look more "alike".
If your sql statements are generated by code, then that removes
the need of a special case for updates.
greetings, Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2006-07-27 15:43:40 | Re: [HACKERS] Resurrecting per-page cleaner for btree |
| Previous Message | Florian G. Pflug | 2006-07-27 15:39:21 | Re: GUC with units, details |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2006-07-27 15:43:40 | Re: [HACKERS] Resurrecting per-page cleaner for btree |
| Previous Message | Rocco Altier | 2006-07-27 15:35:26 | Re: [HACKERS] [COMMITTERS] pgsql: /contrib/cube improvements: |