#26786: Redundant range validators on integer fields
-------------------------------------+-------------------------------------
Reporter: e-stepanov | Owner:
| e-stepanov
Type: Bug | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: IntegerField, | Triage Stage: Ready for
validators, MaxValueValidator | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"49b4596cb4744e4b68d56e6a540a3e15c1582963" 49b4596]:
{{{
#!CommitTicketReference repository=""
revision="49b4596cb4744e4b68d56e6a540a3e15c1582963"
Fixed #26786 -- Avoided redundant max value validators on integer fields.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26786#comment:7>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.6cf8bf60e79f99a5faf14c29a3fe879b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
