Problem on db-api page - partial conversion of author ForeignKey to ManyToMany
| Reported by: |
Collin Grady <cgrady@…> |
Owned by: |
Jacob |
|
Component:
|
Documentation
|
Version:
|
dev
|
|
Severity:
|
|
Keywords:
|
|
|
Cc:
|
|
Triage Stage:
|
Ready for checkin
|
|
Has patch:
|
yes
|
Needs documentation:
|
no
|
|
Needs tests:
|
no
|
Patch needs improvement:
|
no
|
|
Easy pickings:
|
no
|
UI/UX:
|
no
|
It appears that the Entry/Author example started to be changed into a ManyToMany instead of a ForeignKey, but not all of the examples were updated - in one of them, it is still doing entry.author = joe instead of entry.authors.add(joe).
Change History
(5)
| Patch needs improvement: |
set
|
| Triage Stage: |
Unreviewed → Accepted
|
| Patch needs improvement: |
unset
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Resolution: |
→ fixed
|
| Status: |
new → closed
|
I think it's still important to show an example of saving a FK there, so the FK example should be changed to show
.blogbeing modified, then the M2M example after that.