#35077: Quering with int that has bigint in database no longer working.
-------------------------------------+-------------------------------------
Reporter: Matej Spiller Muys | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Matej Spiller Muys):
I agree that this is dangerous behaviour. But if you model django after
existing database it can happen.
It is perfectly fine and appreciated to expose such problems. But hidding
the problem into sometihing that seems like a valid result, it is not.
It seems that
https://github.com/django/django/commit/dde2537fbb04ad78a673092a931b449245a2d6ae
overflow or underflow triggers empty recordset esentially hiding the
problem.
I would expect under or overflow exception to be propagated to the caller.
--
Ticket URL: <https://code.djangoproject.com/ticket/35077#comment:3>
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/0107018cc6cbcce8-b29cd29b-ffa5-4ac3-b1b7-d4db81827b6a-000000%40eu-central-1.amazonses.com.
