#11265: ForeignKey/OneToOneField should support user-defined id attribute name
-------------------------------------+-------------------------------------
Reporter: dstora | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version:
(models, ORM) |
Severity: Normal | Resolution:
Keywords: foreign key | Triage Stage: Accepted
ForeignKey OneToOneField id |
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by collinanderson):
* cc: cmawebsite@… (added)
Comment:
We're moving in the direction of having two distinct fields here. One
that's simply an "id" field, and one that's the ForeignKey. This would
control the name of the underlying field.
--
Ticket URL: <https://code.djangoproject.com/ticket/11265#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.df1b2cbeb60556d080b99e13715a7408%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
