On Sunday, June 21, 2015 at 11:17:25 AM UTC+2, Aymeric Augustin wrote:
>
> (...)
> I think we should provide the best API for our users and deal with the
> code.
> I’m in favor of not introducing another class and figuring out the least
> awful
> way to arrange the code paths in DecimalField.
“Unlimited” precision is a natural semantic DecimalField(). Likewise, if we
ever make max_length optional in CharField(), now providing it will mean
“unlimited” length. (Scare quotes because storage is never really unlimited.)
I think we should provide the best API for our users and deal with the
Hi,
Django's DecimalField requires both max_digits and decimal_places. Database
backends allow them to be dropped, to specify an "unlimited precision" field.
Adding support for this in Django is probably not very helpful for new apps,
but can help significantly in using Django against legacy da
