#25767: integer_field_ranges are incorrect for MySQL backend
-------------------------------------+-------------------------------------
Reporter: georgemarshall | Owner:
| georgemarshall
Type: Bug | Status: assigned
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by georgemarshall:
Old description:
> The integer ranges for `PositiveSmallIntegerField` and
> `PositiveIntegerField` are reflective of `UNSIGNED INT` and `UNSIGNED
> BIGINT`. When the ORM actually uses `UNSIGNED SMALLINT` and `UNSIGNED
> INT` when creating these fields.
>
> The side effect of this is that data will pass validation checks, but
> fail to commit to the database.
New description:
The integer ranges for `PositiveSmallIntegerField` and
`PositiveIntegerField` are reflective of `UNSIGNED INT` and `UNSIGNED
BIGINT`. When the ORM actually uses `UNSIGNED SMALLINT` and `UNSIGNED INT`
when creating these fields.
The side effect of this is that data will pass validation checks, but will
be munged by the database.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/25767#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.4f2ec66d3f170a1221a51c148d6eba70%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
