Changes between Initial Version and Version 2 of Ticket #32577


Ignore:
Timestamp:
Mar 21, 2021, 7:09:46 AM (3 years ago)
Author:
Tomasz Wójcik
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #32577

    • Property Summary Don't enforce `DEFAULT_AUTO_FIELD` to subclass from `AutoField` → Add support for `UUIDAutoField` `DEFAULT_AUTO_FIELD`

  • Ticket #32577 – Description

    initial v2  
    4545
    4646I'm happy to open a PR once I know what's the desired functionality. Possible solutions I see:
    47 - enforce subclassing from `AutoFieldMixin` instead of `AutoField`
    48 - I don't think this field has to be very generic because DB pk types are very limited. As far as I know, only ints and UUIDs make sense for pk. Maybe adding `UUIDAutoField` to django fields would make sense. That way it'd have to enforce subclass of `AutoField` or `UUIDAutoField`
     47- enforce subclassing of `AutoFieldMixin` instead `AutoField`
     48- I don't think this field has to be very generic because DBs pk types are very limited. As far as I know, only ints and UUIDs make sense for pk. Maybe adding `UUIDAutoField` to django fields would make sense. That way it'd have to enforce subclass of `AutoField` or `UUIDAutoField`
    4949
    5050Mentioned also in [https://groups.google.com/g/django-developers/c/MBPEPKlibGQ/m/uJVZbMpqBAAJ here], [https://groups.google.com/g/django-developers/c/MBPEPKlibGQ/m/ntEoLCCMBAAJ here] and [https://github.com/django/django/pull/13179#issuecomment-742473840 here].
Back to Top