#36030: SQLite backend: division with Decimal("x.0") operand discards fractional
portion of result
-------------------------------------+-------------------------------------
     Reporter:  Bartłomiej Nowak     |                    Owner:  VIZZARD-X
         Type:  Bug                  |                   Status:  assigned
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  division             |             Triage Stage:  Accepted
  decimalfield sqlite                |
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  1                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by VIZZARD-X):

 Update: The patch for skipping the unnecessary CAST(... AS NUMERIC) on
 literal Value(Decimal(...)) expressions for SQLite is now submitted in
 PR: https://github.com/django/django/pull/20309

 All unrelated backend tests pass. The remaining failures in the Windows +
 SQLite + Python 3.14 jobs appear to come from areas outside this change
 (duration functions and form constraint validation), and not from the
 SQLiteNumericMixin.as_sqlite() logic or the regression test added for this
 ticket.

 If needed, I can open a separate ticket to track those unrelated
 Windows/SQLite issues.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36030#comment:42>
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 visit 
https://groups.google.com/d/msgid/django-updates/0107019abb7fece2-19fc7e61-e208-41ad-8a4a-4f92999cf94d-000000%40eu-central-1.amazonses.com.

Reply via email to