#2365: [patch] models.FloatField should be renamed
-------------------------------+--------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: Database wrapper | Version:
Severity: normal | Resolution:
Keywords: |
-------------------------------+--------------------------------------------
Comment (by [EMAIL PROTECTED]):
+1 on
1) Renaming FloatField to DecimalField (and make it consistently Decimal
across databases).
2) Creating a new FloatField that is indeed a floating point value
(according to what databases provide).
I would say 1 is essential, 2 is nice to have.
--
Ticket URL: <http://code.djangoproject.com/ticket/2365#comment:>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
