ak wrote:
A bit more info:
print user.tariff.monthly_fee.__class__, user.balance.__class__,
user.tariff.monthly_fee, user.balance, user.tariff.monthly_fee/3 >
user.balance
displays:
<class 'decimal.Decimal'> <type 'float'> 180.00 1846.85 True
while 180/3 = 60 which is ofcourse less than 1846.85 so it should
display False in the last column
I've run into this: Django's FloatField is not really a Python float.
It creates a SQL numeric field in the DB. MySQLdb then maps the MySQL
numeric field to a Python decimal.Decimal value so that it retains the
full precision and range of the field. A Python float and
decimal.Decimal are not the same type and are not directly compatible:
import decimal
d = decimal.Decimal(180)
d
Decimal("180")
f = float(180)
d == f
False
float(d) == f
True
I wish there were a way to either (1) tell Django to use a real SQL
float field, or (2) tell MySQLdb to map the SQL numeric field to a
Python float, but I just live with the annoyance of doing wrapping all
my numeric model fields in float() all over my code.
I'm sure there is a better way and odds are that Malcolm will know it!
;-)
-Dave
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
