#2365: [patch] models.FloatField should be renamed
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Database wrapper
Version: | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------+------------------------------------------
Comment (by [EMAIL PROTECTED]):
* PostgreSql behavior seems to be analogous to that of MySQL. Using
FloatField worked with SQLite for floating point values, but 'broke'
(i.e., worked properly) when we tried to insert a floating point number
into a NUMERIC field.
* SQLite behavior occurs because Sqlite puts whatever value it's passed
into the database if it can't do a conversion to the defined type - field
types in the table definitions are hints, but they are not strictly
enforced. See [http://www.sqlite.org/faq.html#q3]. It's a feature.
* We are developing a system that requires the use of floating point
numbers in the database. We probably have to use this patch (which is
preferable to an ugly workaround) in order to move forward on our project.
--
Ticket URL: <http://code.djangoproject.com/ticket/2365#comment:25>
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
-~----------~----~----~----~------~----~------~--~---
