On 28 sept. 2014, at 19:57, Simon Riggs <si...@2ndquadrant.com> wrote:

>> 1) The django-developers mailing list isn't the place to rehash the debate,
>> 2) The disparaging vocabulary you're using isn't acceptable in this forum,
>> 3) Personal attacks based on prejudice will not be tolerated.
> 
> Well, for 1) any comments are most welcome.

provided they relate to Django and are based on facts rather than rhetoric :)

As explained above, Django could take advantage of ON DUPLICATE to
implement create_or_update with good database level guarantees.

It isn't clear what Django could do with MERGE. Maybe a suggestion will
come later in the thread.

At this point, as far as Django is concerned, Peter's proposal aligns well
with what our users ask for.

> I didn't see any evidence of the other two.

Perhaps comparing the email I reacted to with the following proposal will help:

"Obviously the PostgreSQL project can make its own choices. But I'm surprised
that you're proposing non-standard syntax and semantics, considering
PostgreSQL's tradition to comply with SQL standards. Even if you disagree with
some aspects of the specification of MERGE, wouldn't it be valuable to
implement it properly? Since I'm not the most knowledgeable person on this
topic, where can I learn more about the reasons for this choice?"

(I've had to add one idea to base the argumentation on at least one fact.
Otherwise the ideas are the same in the same order.)

-- 
Aymeric.




-- 
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/EA742E1F-B03F-467B-A508-D07CE3F33E95%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to