id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux 15678 Different behaviour for DecimalField on MySQL and SQLite max@… nobody "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 ?" New feature closed Database layer (models, ORM) 1.3 Normal needsinfo sqlite, mysql, decimalfield Accepted 0 0 0 0 0 0