Opened 9 years ago
Last modified 9 years ago
#25767 closed Bug
integer_field_ranges are incorrect for MySQL backend — at Version 4
| 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 (4)
comment:1 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 by , 9 years ago
| Cc: | added |
|---|
comment:4 by , 9 years ago
| Description: | modified (diff) |
|---|
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.