integer_field_ranges are incorrect for MySQL backend
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.
Owner: |
changed from nobody to George Marshall
|
Status: |
new → assigned
|
Triage Stage: |
Unreviewed → Accepted
|
Description: |
modified (diff)
|
Has patch: |
set
|
Patch needs improvement: |
set
|
Resolution: |
→ fixed
|
Status: |
assigned → closed
|
Since this a bug in a new feature (introduced in 1.8) that can possibly lead to data loss I think this is worth a backport.