#28926: some big values of DurationField are saved inaccurately on SQLite and
MySQL
-------------------------------------+-------------------------------------
Reporter: Sergey Fedoseev | Owner: Sergey
| Fedoseev
Type: Bug | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ae6fa914aa2f43d39ae491ac7d3140dda69702fa" ae6fa914]:
{{{
#!CommitTicketReference repository=""
revision="ae6fa914aa2f43d39ae491ac7d3140dda69702fa"
Fixed #28926 -- Fixed loss of precision of big DurationField values on
SQLite and MySQL.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28926#comment:5>
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/068.df8b96774e7f47543ec4198bc70f9603%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
