Re: Merge condition in postgresql

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Amit jain <amitjain(dot)bit(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Merge condition in postgresql
Date: 2008-02-04 16:09:50
Message-ID: 20080204160950.GB17150@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 04, 2008 at 09:44:17AM -0600, Roberts, Jon wrote:
> If you guys develop Merge for PostgreSQL, I highly suggest putting an
> "order by" statement in the syntax so if the source has duplicates, it
> will insert the first one and then do subsequent updates.

I don't think it would meet the standard definition then. The statement
shouldn't be able to to see the effects of itself...

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Those who make peaceful revolution impossible will make violent revolution inevitable.
> -- John F Kennedy

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2008-02-04 16:20:08 Re: pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59
Previous Message Simon Riggs 2008-02-04 16:04:43 Page-at-a-time Locking Considerations