I am not Agree. qs1.all() it is copy from qs1, the new object.
I already try to write QuerySet compare on the Django 1.4 and i remember, that str(qs1.query) can be different as str(qs2.query), I am not Shure. Mit freundlichen Grüßen, DI Mag. Maxim Danilov +43(681)207 447 76 <mailto:[email protected]> [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of mohamad ali mehdizadeh Sent: Tuesday, May 10, 2022 5:09 PM To: Django developers (Contributions to Django itself) <[email protected]> Subject: Equality check for two QuerySet Hi. Why we don't have __eq__ for QuerySets, here is an example: ``` qs1 = Model.objects.all() qs2 = qs1.all() qs1 == qs2 ``` output: False as we know these two are the same by value! -- 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 [email protected] <mailto:[email protected]> . To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/80e878f8-8701-40ad-92a0-5c689df27ec2n%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/80e878f8-8701-40ad-92a0-5c689df27ec2n%40googlegroups.com?utm_medium=email&utm_source=footer> . -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/000801d864a5%24b65b5550%242311fff0%24%40wpsoft.at.
