Opened 16 years ago
Closed 16 years ago
#7690 closed (wontfix)
obj.manytomanyrel = None no longer works, needs reference in BackwardsIncompatibleChanges
| Reported by: | dnordberg | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
It used to be that a manytomany relationship could be assigned to None, which would be the same as calling clear().
E.g. obj.manytomanyrel = None was the same as obj.manytomanyrel.clear().
I think this was also in the documentation.
Now I cant do obj.manytomanyrel = None. I can however do this, obj.manytomanyrel = [].
I think needs to be added to db-api and BackwardsIncompatibleChanges.
Change History (2)
comment:1 by , 16 years ago
| Component: | Uncategorized → Documentation |
|---|
comment:2 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I honestly can't recall that this ever worked, but I'll take your word for it! However, it shouldn't have worked in the first place; the fact that it did was probably a bug.