#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 Luke Plant):
I agree we should try to automatically resolve the type. 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 e.g. the database actually casts to the smaller of the type, or
the first type. In this case, the user may need to know that it isn't
going to do what you expect.
--
Ticket URL: <https://code.djangoproject.com/ticket/34160#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/010701847ce28581-935fa773-ae35-424d-86a6-56166b63938a-000000%40eu-central-1.amazonses.com.
