#29979: Refactor AutoField logic into a mixin, implement checks and validators.
-------------------------------------+-------------------------------------
     Reporter:  Nick Pope            |                    Owner:  Nick Pope
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  autofield,           |             Triage Stage:  Accepted
  validators                         |
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"21e559495b8255bba1e8a4429cd083246ab90457" 21e5594]:
 {{{
 #!CommitTicketReference repository=""
 revision="21e559495b8255bba1e8a4429cd083246ab90457"
 Fixed #29979, Refs #17337 -- Extracted AutoField field logic into a mixin
 and refactored AutoFields.

 This reduces duplication by allowing AutoField, BigAutoField and
 SmallAutoField to inherit from IntegerField, BigIntegerField and
 SmallIntegerField respectively. Doing so also allows for enabling the
 max_length warning check and minimum/maximum value validation for auto
 fields, as well as providing a mixin that can be used for other possible
 future auto field types such as a theoretical UUIDAutoField.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29979#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9a4c3a77fef47fbf62d92567fede275c%40djangoproject.com.

Reply via email to