On Tue, Sep 30, 2014 at 12:49 AM, Anssi Kääriäinen <anssi.kaariai...@thl.fi> wrote: > Both PostgreSQL's proposed documentation and MySQL's > existing documentation warn users that it is a bad idea to use this > feature when multiple unique indexes exists for the table. So, why make > that behavior default?
The MySQL documentation is mostly due to INSERT...ON DUPLICATE UPDATE completely breaking their statement-based replication. I accept that there are other hazards, but it's difficult to have a fully general syntax that indicates user intent WRT the unique index to merge on. -- Peter Geoghegan -- 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/CAM3SWZTBiWRN4Am9deegPLoJjZa4SdzPJ4wGhL7StDLAf4MZRw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
