#25417: decimal.InvalidOperation caused by Migrations and DecimalField()
-------------------------------------+-------------------------------------
Reporter: avorio | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution: needsinfo
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
-------------------------------------+-------------------------------------
Changes (by charettes):
* status: new => closed
* resolution: => needsinfo
Comment:
I couldn't reproduce against master and 1.8.4 on Python 3.4 with SQLite
with the following steps:
1. Create an app with a single model with a decimal like specified above;
2. Create the initial migration for the app and run it;
3. Change the model field like specified above;
4. Create the new migration and run it.
Which database backend are you using?
--
Ticket URL: <https://code.djangoproject.com/ticket/25417#comment:4>
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.99edcaf8c0e70b5bbae1a97fbb01ed59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
