#36574: Regression: DecimalField values are no longer quantized before written
to
the DB
-------------------------------------+-------------------------------------
Reporter: Aaron Mader | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: decimal_places | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* keywords: => decimal_places
* resolution: => invalid
* status: new => closed
Comment:
Agree with the above assessments.
The [https://docs.djangoproject.com/en/5.2/releases/5.2/#database-backend-
api release note] describes this bugfix as relevant only to third-party
database backends, so although we don't normally document bugfixes, I
could be open to an addition to indicate that silent truncation no longer
happens when values are prepped for insertion, since we have this report
of a user relying on it.
--
Ticket URL: <https://code.djangoproject.com/ticket/36574#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198f0d9f4b6-a1835abe-a26b-47f9-a2ee-affaed2d818e-000000%40eu-central-1.amazonses.com.
