On Sep 28, 2014, at 11:21 AM, Peter Geoghegan <p...@heroku.com> wrote:
> On Sun, Sep 28, 2014 at 1:51 AM, Petite Abeille > <petite.abei...@gmail.com> wrote: >> For diversity's sake, and for the record, I, for one, would definitively >> rather have the standard MERGE statement instead of yet another 'weird' >> UPSERT concoction peculiar to Postgres. > > A few people have said that, but then when you look at SQL MERGE in > detail it becomes apparent that it is really intended to serve the > bulk loading use-case. A bad case of confirmation bias :D > I took the time to delineate the differences > between SQL MERGE and what I call UPSERT in detail [1]. Again, your house, your choice. But it seems a bit self-indulgent to concoct your very own take on MERGE, with baroque syntax, peculiar semantic, and all, just because some abstract aspects of the MERGE specification is not to you liking... rather self-defeating altogether. Anyway, just my 2¢. -- 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/6F5E6744-BE21-43EA-A11E-EF8D9CF5E5C0%40gmail.com. For more options, visit https://groups.google.com/d/optout.
