#10251: Problem with inheritance plus explicit primary_key in child model
---------------------------------------------------+------------------------
Reporter: kmtracey | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by Alex):
I'm of the opinion that the value in supporting this is severely out
weighed by the value in not supporting it, specifically if we don't
support it we can do nifty optimizations like what I posted in #9394 all
the time. As best I can tell the only point of supporting this would
essentially be for the model to have 2 primary keys(2 not null unique
fields) you can still keep the extra field, put an index on it, whatever,
but giving it the primary key semantic is more trouble than it's worth.
--
Ticket URL: <http://code.djangoproject.com/ticket/10251#comment:2>
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
