Hi, I'm creating this topic to see if there is interest to implement positional arguments in queryset filtering.
Current situation Currently the only way to use positional arguments to filter can be either: - Passing a single or multiple Q objects: MyClass.objects.filter(Q(key=value)) MyClass.objects.filter(Q(key=value), Q(other_key=value)) - Passing a couple is also working (not sure if this is a happy accident, should it be removed?) MyClass.objects.filter((key, value)) - Combination of both is also proven to work MyClass.objects.filter((key, value), Q(other_key=value)) Suggestion This feature suggestion is to leverage the case when a non-Q / non couple object is passed, so it implicitly interpreted as the value for the model's pk. This could ease/simplify code by omitting pk when this is the only filter used: MyClass.objects.get(value) # Translates into: MyClass.objects.get(pk=value) or MyClass.objects.filter(value) # Translates into: MyClass.objects.filter(pk=value) or MyClass.objects.filter(Q(value)) # Translates into: MyClass.objects.filter(Q(pk=value)) Do you think it's worth it? It could be leveraged to simplify many situations. I'd be happy to proceed to the development myself if this is something gathering interest. -- 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/b30b52f4-479b-4342-885b-2ce78af6f70e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
