I have to say, the lack of __ne is very inconsistent for people new to django, but veterans at sql. It's just one more frustration point when you're trying to learn a new ORM.
-Ben On Friday, November 20, 2015 at 11:37:02 AM UTC-8, Carsten Fuchs wrote: > > Hi all, > > sorry if this is a stupid question, but after having read > https://code.djangoproject.com/ticket/5763 and the discussions linked > from it, why should __ne not be implemented? > > Without __ne, I'm experiencing the same problems that asmoore82 described > at https://code.djangoproject.com/ticket/5763#comment:23 > That is, afaics, some queries cannot be formulated without __ne, as > exclude() is not an equivalent. Or am I missing or misunderstanding > something? > I can live with the existing work-arounds, so I'm mostly curious. :-) > > Best regards, > Carsten > > -- 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/d227ef16-be32-4b6e-8fe7-f91ea5979ee1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
