Deprecate UserManager managing AbstractBaseUser objects?

Hi list, I picked up an optimization from the backlog proposing to move the method normalize_email() from BaseUserManager to AbstractUser, where the email field is defined. The proposal involved a deprecation period for users who rely on the curren

Guardrails around lack of model validation on blank=True fields

Hi group, We have several accepted tickets regarding developer headaches when a blank=True field, which skips model validation by design[1], contains inappropriate empty values (e.g. None for a not-nullable field or the empty string where empty strings aren't allowed). I want to see what the

Re: Guardrails around lack of model validation on blank=True fields

This makes good sense, Carlton, and I didn't mean to be rushing your reply! "That way lies madness" is entirely correct. Just wanted to map the terrain after I had so confidently commented on one Trac ticket about wontfix-ing it, since on it there were various opinions about possible courses of

Re: Optimization for get_search_results() in admin

Hi list, I came to suggest a resolution for the above: the potential for impossible (or resource-gobbling) queries in admin changelist searches. (Ticket ) Several folks have proposed the same solution: AND’ing Q objects together rather than chain