#2365: [patch] models.FloatField should be renamed
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Database wrapper
Version: | Resolution:
Keywords: | Stage: Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------+------------------------------------------
Comment (by [EMAIL PROTECTED]):
Added an updated patch against r4439.
* db.FloatField handle only floats, and db.DecimalField handle only
decimals.
* oldforms.FloatField and oldforms.DecimalField are the defaults for the
db fields and do the Right Thing validation-wise
* newforms.FloatField and newforms.DecimalField ditto; but they also
support max_value and min_value arguments à la newforms.IntegerField
This patch includes tests for both the database fields and the form
fields.
--
Ticket URL: <http://code.djangoproject.com/ticket/2365#comment:17>
Django Code <http://code.djangoproject.com/>
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 [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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
