#33232: DecimalField rounding error when upgrading from 3.1 to 3.2 on Postgres
-------------------------------------+-------------------------------------
Reporter: Michał Szczepańczyk | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: decimal, | Triage Stage:
decimalfield, rounding, postgres | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:3 Michał Szczepańczyk]:
> That's for the response. In such case I think it would be good to
mention the change in release docs.
I will try to figure out how to mention it in docs.
> Another consequence of this change is that we have different results
between sqlite and postgres. When using sqlite the following query is
generated:
> {{{
> INSERT INTO "myapp_foo" ("amount") VALUES ('1.12')
> }}}
Yes but it returns `1.13` as in MySQL and Oracle.
--
Ticket URL: <https://code.djangoproject.com/ticket/33232#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.916355e92655141a9b6a7de297919365%40djangoproject.com.
