On Sun, Jan 10, 2016 at 5:22 PM, Sean Brant <brant.s...@gmail.com> wrote:
> I've always considered this a bug waiting to happen. I have seen many errors > with the get operation failing because it returned more then one value. > Usually you don't notice the error until you hit production. I always > suggest the lookup use fields that have unique indexes. > > Changing that would be backwards incompatible so maybe it's a docs issue. If there are no valid use cases for using get_or_create() without an unique index, then we could consider doing a backwards incompatible change here. I believe there are cases where you want to do a get_or_create() without unique index (though I can't come up with one right now). We could always check if there is a backing unique index and use get_or_create only in those cases. - Anssi -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALMtK1EbwD7hJLFOjsiUeMxofov9zwRbX_Zr%2BZArqdy%2Bj_fT_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
