#24472: Define internal types explicitly for related fields
-------------------------------------+-------------------------------------
Reporter: Andriy Sokolovskiy | Owner: Akash
| Kumar Sen
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => wontfix
* stage: Accepted => Unreviewed
Comment:
I don't see a real use case for adding this. Moreover, others do not seem
too convinced either and it can cause issue for custom subclasses of
related fields. As far as I'm aware, it's not worth changing this long-
standing behavior and potential hiccups.
--
Ticket URL: <https://code.djangoproject.com/ticket/24472#comment:8>
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/010701889e803533-e90e3a45-32fd-4f88-8c2e-4861fc9a8363-000000%40eu-central-1.amazonses.com.
