#32793: Problem with decimal field when upgrade version
-------------------------------------+-------------------------------------
Reporter: Mohsen Tamiz | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: decimal | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"94675a76339f98ed6fa9d07d4e647f8ef33953a0" 94675a76]:
{{{
#!CommitTicketReference repository=""
revision="94675a76339f98ed6fa9d07d4e647f8ef33953a0"
[3.2.x] Fixed #32793 -- Fixed loss of precision for temporal operations
with DecimalFields on MySQL.
Regression in 1e38f1191de21b6e96736f58df57dfb851a28c1f.
Thanks Mohsen Tamiz for the report.
Backport of e703b152c6148ddda1b072a4353e9a41dca87f90 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32793#comment:12>
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/063.1355ec20095b9e6a1fe8dac9fda16ebb%40djangoproject.com.
