I think I've worked it out now. I'd defined the field wrong (didn't match database type). It loaded fine, but when I tried to save the same data django rejected it.
2009/7/2 Shawn Milochik <shawn.m...@gmail.com>: > > Would you post the model and the relevant parts of the form and/or view? > > In any case, you can easily fix it by following the error message's > suggestion of str(your_float). But if you think there's a discrepancy > between the way your fields are behaving, post some code and we'll see > if we can figure it out. > > Shawn > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
