On Wed, Apr 27, 2011 at 2:44 AM, Conrad Calmez <[email protected]> wrote: > two weeks ago I started fixing the ticket #4287. It appears that > infinity values can not be stored to FloatFields using MySQL (that is > what I reproduced). I found out that MySQL can not handle infinity > values. My Fix uses the minimal and maximal float values > (-2147483648 / 2147483647) as -inf/inf. > My questions is if that way of fixing this bug is acceptable. If so I > will also try to reproduce/fix this bug for other db backends.
I really don't think that's a good idea. "Magic" numbers are rather gross, and 2147483647 is a long way from +inf. If MySQL can't support inf/-inf, then Django can't, either. About the only thing we should do in that case is throw a better exception. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
