Changes between Initial Version and Version 1 of Ticket #19061, comment 4
- Timestamp:
- Oct 4, 2012, 11:45:05 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #19061, comment 4
initial v1 1 One potential issue with the property approach is that it a non-field implementation will prevent the use of is_active in querysets - this won't break current User.objects.filter(is_active=True) usage on existing auth.User objects, but will limit an optimized approach that use user object neutral.1 One potential issue with the property approach is that a non-field implementation will prevent the use of is_active in querysets - this won't break current User.objects.filter(is_active=True) usage with existing auth.User objects, but will limit an optimized approach that can be used in a universal user-object-neutral way. 2 2 3 3 Part of the issue in making this call is the very messy history is_active has had in the way people have struggled with a clear definition of what it means: