Context Navigation

Changes between Version 3 and Version 4 of Ticket #35410, comment 3

v3	v4
1	1	Maybe I ask you are not simply `NULL` to denote the lack of assignment? Trying to perform database operations in a `Field.default` callback is doomed to fail in a myriad of ways [https://docs.djangoproject.com/en/5.0/ref/models/fields/#django.db.models.Field.default hence why the documentation suggests that a literal value be returned instead].
2	2
3		I think we should adjust [https://github.com/django/django/blob/828b94b178736f7882cc6e5cd86b5c8e84b62ece/django/contrib/auth/checks.py#L84-L103 the checks] to avoid creating user model instances at check time but there are tons of ways why the pattern you are using now might break.
	3	I think we could adjust [https://github.com/django/django/blob/828b94b178736f7882cc6e5cd86b5c8e84b62ece/django/contrib/auth/checks.py#L84-L103 the checks] to avoid creating user model instances at check time but there are tons of ways why the pattern you are using now might break.