On Fri, Nov 13, 2009 at 11:52 AM, ses1984 <ses1...@gmail.com> wrote: > Here's the traceback. >
Traceback shows the error is being raised during save of an existing object. So forget all the formset stuff and focus on the question that raises: can you re-save an instance of this model right after retrieving it from the database? Try it from a python manage.py shell session: >>> from <yourapp>.models import Retain >>> r = Retain.objects.all()[0] >>> r.save() I suspect you'll get the same error raised, which indicates there's a mismatch in how the model is defined to Django as compared to how it is defined to the database. The amount field in the model is declared as a DecimalField, but the data coming from the database appears to be a float. Either the Django field should be a FloatField or the database table needs to be converted to use a type that will appear on the Python side as a Decimal. If you don't get the same error raised on a simple attempt to re-save an existing object, then it would be time to start digging into the formset stuff to see why the results when using a formset differ from not. Karen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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=.
