On 8/9/07, Vincent Foley <[EMAIL PROTECTED]> wrote: > > Hello, > > I found a curious problem in my application when I put it into > production this week: when a models.FloatField is "extracted" from the > database, its type changes depending on the database. With SQLite in > development, I got back floats, while on MySQL in production I have > decimals. As mentionned in other posts, decimals are not serializable > in JSON.
For the record - current trunk has no problem serializing Decimal fields or Float fields. > We are using Django 0.96 (and have no intention to use the Subversion > branch.) Is it possible to fix the problem without applying a patch? > I don't have root access to the production environment, so I can't > apply patches. Not really, no. What you are seeing is a known issue caused by the way that we handled FloatFields. If you can't patch the version of Django, there isn't really anything you can do in a clean way to fix the problem. This problem was fixed in [5302] (which is post 0.96). See the following for more details: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RenamedFloatFieldtoDecimalField Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
