#25417: decimal.InvalidOperation caused by Migrations and DecimalField()
-------------------------------------+-------------------------------------
Reporter: avorio | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution:
Keywords: decimal, | Triage Stage:
InvalidOperation, migrations | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
I guess an extra check wouldn't hurt here.
I thought adding `Field.check_default` method running
`field.validate(field.get_default(), None)` and making sure no
`ValidationError` is raised would make sense but in this case the float is
silently converted to a `decimal.Decimal`.
{{{#!python
>>> from django.db.models import DecimalField
>>> DecimalField().validate(20.5, None)
>>> DecimalField().to_python(20.5)
Decimal('20.5')
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25417#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.8aa1d710299a77e549e0b61fc608192c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
