On Sat, Jan 07, 2006 at 02:16:46PM -0500, [EMAIL PROTECTED] wrote: > Isaac Raway <[EMAIL PROTECTED]> wrote: > > [I]nstead of dropping the row existing, [the REPLACE algorithm should] > > simply update the provided fields in place, leaving the unmodified fields > > as is. I'd call this behavior OR UPDATE as it would be exactly equivalent > > to doing an UPDATE on the existing row(s). > > There might be two or more rows that conflict. How would it choose > which row to use as the basis?
Not according to the original email... > When a UNIQUE constraint violation occurs, the pre-existing rows that are causing the constraint violation are removed prior to inserting or updating the current row. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
