#25767 closed Bug (fixed)
integer_field_ranges are incorrect for MySQL backend
| Reported by: | George Marshall | Owned by: | George Marshall |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.8 |
| Severity: | Normal | Keywords: | |
| Cc: | Simon Charette | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
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.
Change History (9)
comment:1 Changed 8 years ago by
| Owner: | changed from nobody to George Marshall |
|---|---|
| Status: | new → assigned |
comment:2 Changed 8 years ago by
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 Changed 8 years ago by
| Cc: | Simon Charette added |
|---|
comment:4 Changed 8 years ago by
| Description: | modified (diff) |
|---|
comment:5 Changed 8 years ago by
| Has patch: | set |
|---|---|
| Patch needs improvement: | set |
Tests aren't passing on the pull request and I left some comments for improvement.
Note: See
TracTickets for help on using
tickets.
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.