Changes between Version 1 and Version 2 of Ticket #28594, comment 6
- Timestamp:
- May 15, 2025, 9:30:35 AM (4 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #28594, comment 6
v1 v2 1 1 Hi, and thanks for the opportunity to look into this ticket. 2 2 3 It seems that the issue has already been addressed in some form (via documentation updates), and it may have just been left open by oversight. In any case, the problem is no longer present in supported Django versions — as of 3.0, using a ForeignKey for USERNAME_FIELD is unsupported.3 It seems that the issue has already been addressed in some form (via documentation updates), and it may have just been left open by oversight. In any case, the problem is no longer present in supported Django versions — as of [https://docs.djangoproject.com/en/3.0/topics/auth/customizing/#django.contrib.auth.models.CustomUser.USERNAME_FIELD 3.0], using a ForeignKey for USERNAME_FIELD is unsupported. 4 4 5 5 Given that, I would suggest closing this ticket as either resolved or invalid, unless there’s still something outstanding I may have missed.