I know this is a crazy idea, and it will get the "won't fix" tag very soon.
Nevertheless I want to speak it out. My use case: Get a queryset of users who have a given permission. I would like to get this with a simple SQL statement. At the moment this query is complex and results in performance issues, since several outer joins get created. See: https://groups.google.com/forum/#!topic/django-users/lUGkZybXllM is_superuser and is_staff could be changed to permissions easily. It's different with is_active. But again: a simple SQL to get all users which have a given permission is my goal. I personally could live without is_active: Just remove all permissions for this user. If you don't like dropping all perms to make a user inactive since you want to switch back and forward between active and inactive ... then this a different (bigger) problem: switching back and forward between states. Why not solve this for all models (not just User instances)? But this is a different topic :-) I know the road to deprecate these three friends would be hard since a lot of code uses them. What do you think? -- 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 post to this group, send email to [email protected]. 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/961fd91c-3954-4c7f-a05e-807f2863dc5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
