On Sep 29, 2014, at 2:46 PM, shmengie <1st...@gmail.com> wrote: > Merge -- bulk loading foreign data -no guaranty > > upsert -- insert or update row w/confidence.
Sounds like a difference without a distinction. Let spin it a different way: the MERGE syntax, and broad semantic, is fine as it is, for all use cases, in all its ISO glory. There is no compelling reasons to invent another one. The only point of contention is what guaranty, if any, the MERGE statement provides, which is formally none. The UPSERT statement as suggested identify a narrow use case where it can provide some sort of guaranties about atomicity and race condition [1]. Beautiful. Let this be an implementation detail of MERGE as understood by Postgres: under the right circumstances, Postgres' MERGE implementation guaranties such and such. This is a compelling implementation advantage. But not one that warrant a different syntax and semantic altogether. My 2¢. [1] http://www.depesz.com/2012/06/10/why-is-upsert-so-complicated/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/45E95C5A-31CE-4177-82A4-1BBCB0F0A5EA%40gmail.com. For more options, visit https://groups.google.com/d/optout.
