Opened 19 years ago
Last modified 18 years ago
#230 closed defect
FloatField with MySQL Backend fails silently — at Initial Version
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.0 |
| Severity: | major | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
If I have a FloatField with a particular precision, and I submit a form that has higher precision than I specified when creating the model, it will fail silently. When I say fail silently, and error is raised but no description is passed out of the validator. An example model :
meta.FloatField('latitude', max_digits=10, decimal_places=7, default=0.0),
meta.FloatField('longitude', max_digits=10, decimal_places=7, default=0.0),
And then if I have an input that is either more than 10 digits or 7 decimal places, it will fail.
I'm not sure where I could insert any rounding off near the validation model. I was thinking of doing it similar to a typecast as in date/time strings.