Re: [PATCHES] extension for sql update - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [PATCHES] extension for sql update
Date
Msg-id 9EA3B62F-D3BC-44B4-885A-ACCD9EFB4D81@pervasive.com
Whole thread Raw
In response to Re: [PATCHES] extension for sql update  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] extension for sql update
List pgsql-hackers
On Jul 27, 2006, at 7:30 AM, Tom Lane wrote:
> Susanne Ebrecht <miracee@miracee.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.

While the patch doesn't provide any new functionality, I would still
welcome it simply because I find it a lot easier and cleaner to group
fields together when updating multiple fields at once.

Even if we would have to rip this patch back out in order to fully
support the spec, we've got a (mostly) working patch right now, and
it sounds like it would take minimal effort to finish it.

In any case, it sounds like there should be a TODO item out of this.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: GUC with units, details
Next
From: Phil Frost
Date:
Subject: Re: lastval exposes information that currval does not