FloatField with MySQL Backend fails silently

[alastair@…]

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.

[Adrian Holovaty]

(Fixed formatting in description.)

[Malcolm Tredinnick]

This has been fixed at some indeterminate point in the past, I believe. We raise a validation error (with an error string) when either the whole part or the decimal part or the entire float fail to meet validation requirements. "Rounding off" as specified near the end of the report is the caller's responsibility.

[(none)]

Milestone Version 1.0 deleted