On 11/23/05, David Ascher <[EMAIL PROTECTED]> wrote: > I've had the same problem in cases when I forget to use named parameters to > my FloatFields, which then generates invalid SQL with "None" in it. That's > a bug, IMO. I may even try to fix it =).
As of changeset 1314 (http://code.djangoproject.com/changeset/1314), the model validator (which runs automatically during "django-admin runserver") complains if you don't max_digits and decimal_places on FloatFields. Is it missing an edge case? Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
