Changes between Version 1 and Version 2 of Ticket #36225, comment 11
- Timestamp:
- Sep 25, 2025, 10:42:46 AM (38 hours ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36225, comment 11
v1 v2 1 1 Reopened #35729 as a usability issue in the serialization framework that model subclasses cannot opt out of natural key serialization. 2 2 3 This issue was opened after OP bit the bullet and reimplemented the User model from scratch. I agree it's not correct for createsuperuser to deduce from `field.unique` that we've doc'd that you can deliberately omit `get_by_natural_key()` and also doc'dthat USERNAME_FIELD can be non-unique.3 This issue was opened after OP bit the bullet and reimplemented the User model from scratch. I agree it's not correct for createsuperuser to deduce from `field.unique` that `get_by_natural_key()` exists, given that we've doc'd you can deliberately omit `get_by_natural_key()` and also that USERNAME_FIELD can be non-unique. 4 4 5 5 Catching `AttributeError` here seems reasonable.