Different behaviour for DecimalField on MySQL and SQLite

[max@…]

Consider the following model:

class Product(models.Model):
    title   = models.CharField('Title', max_length=250)
    price   = models.DecimalField('Price', max_digits=9, decimal_places=2, default=0)

If you create or modify an object in the admin using MySQL and set the price to "0" with will automatically become "0.00".

But if you do the same using SQLite3, it will allow it to stay "0".

I know that the two backends doesn't provide the same features support and both store DecimalFiels differently, but couldn't the ORM deal with it transparently ?

[Jacob]

I'm on the fence here - different dbs are different. Is there a compelling argument that we should bother fixing this?

[anonymous]

Well I think Django should abstract databases inconsistencies when it's possible.. since we are perfectionists with deadlines :>

Furthermore in this case we are talking about the representation of a specific data type. So I think it would make sense to handle it with input validation, I don't think that it counts as emulating a missing database feature.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Tim Graham]

I don't understand where the discrepancy is that needs to be fixed.