#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
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* keywords: regression =>
* type: Bug => Cleanup/optimization
Comment:
Maybe we could add a release note to this effect but I don't think we
should be emitting a warning at run time when this happens. Django won't
generate migration or introspect mismatching column and field types so I
think it's safe to expect that things might break if you venture down this
route.
This relates to #27397.
--
Ticket URL: <https://code.djangoproject.com/ticket/35077#comment:2>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cc688e1de-70af438a-6c4a-4c21-b077-4f2f3995eb36-000000%40eu-central-1.amazonses.com.
