#34160: Django 4.1 Expression contains mixed types for (Big/Small)IntegerFields.
-------------------------------------+-------------------------------------
Reporter: Martin Lehoux | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I agree with your suggested solution Markusz. Adding entries to
`_connector_combinations` seems like the way to go for a backport.
> Based on my experience with the related patch, I think it would be worth
checking what MySQL and Postgres do for cases like this - there could be
some unexpected surprises
I know that Postgres will silently cast values outside of the `bigint`
range to `numeric` with [https://code.jeremyevans.net/2022-11-01-forcing-
sequential-scans-on-postgresql.html its unfortunate side effect] so I'm
pretty that it has operators defined to make integer comparison as
implicit as possible.
--
Ticket URL: <https://code.djangoproject.com/ticket/34160#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701847cfc5d71-98ef8194-f702-4888-b85c-6d71a7e57c65-000000%40eu-central-1.amazonses.com.
