#28824: Allow different Foreign Keys to share same underlying DB column
-------------------------------------+-------------------------------------
Reporter: klass-ivan | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: foreigh key, | Triage Stage:
db_column, | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => closed
* resolution: => wontfix
Comment:
Matt, please
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets follow triaging guidelines with regards to
wontfix tickets.]
Moreover this comment is still valid, even with a use case:
> I'm struggling to see where the value for this change would be, and how
common a situation this really is. I think the benefit of supporting this
would be outweighed by users that are incorrectly duplicating keys on
their models with copy/paste and running into legitimate issues.
--
Ticket URL: <https://code.djangoproject.com/ticket/28824#comment:6>
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/068.b1b8f318351437a5141d14c9e3d4a094%40djangoproject.com.
