#13822: ForeignKey's attname is counter-intuitive when referencing to a field
not
named 'id'
---------------------------------------------------+------------------------
Reporter: Suor | Owner: Suor
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: | Keywords: db,
ForeignKey
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by lrekucki):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
First, this change is *very* backwards incompatible, as it would require
to migrate any db schema that has a foreign key.
Second, I hope that someday Django will support multi-column (primary)
keys and it probably won't look so good then.
--
Ticket URL: <http://code.djangoproject.com/ticket/13822#comment:1>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
