Opened 15 years ago
Closed 15 years ago
#11083 closed (invalid)
BackwardsIncompatibleChanges page does not mention OneToOneField change
| Reported by: | Andy Durdin | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | |
| Severity: | Keywords: | wiki | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
After queryset-refactor, OneToOneFields are no longer automatically the primary key of a model. To make older code work post-queryset-refactor, the keyword argument primary_key=True must be added to the field instantiation.
I would have updated the wiki page, but do not appear to have permissions to edit it.
Note:
See TracTickets
for help on using tickets.
http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Queryset-refactormerge It's mentioned on the page linked here, just like the note says.