Code

Opened 8 years ago

Closed 7 years ago

#2264 closed defect (fixed)

docs should mention that delete() cascades

Reported by: mir@… Owned by: jacob
Component: Documentation Version:
Severity: normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

some_model.delete() cascades over ForeignKey constraints. While this is certainly useful, it should be documented in the DB API. At least for me, it came as a surprise.

Attachments (1)

2264.diff (843 bytes) - added by ubernostrum 7 years ago.
Patch documenting the cascading delete

Download all attachments as: .zip

Change History (5)

comment:1 Changed 8 years ago by mtredinnick

This ticket depends upon the outcome of #2288.

comment:2 Changed 7 years ago by SmileyChris

  • Triage Stage changed from Unreviewed to Design decision needed

Changed 7 years ago by ubernostrum

Patch documenting the cascading delete

comment:3 Changed 7 years ago by ubernostrum

  • Triage Stage changed from Design decision needed to Ready for checkin

It seems unlikely that #2288 will be resolved any time soon, and in the meantime people need to know how the delete behavior works, so I'm attaching a patch and bumping to "ready for checkin".

comment:4 Changed 7 years ago by jacob

  • Resolution set to fixed
  • Status changed from new to closed

(In [4636]) Fixed #2264: the docs now mention that delete() cascades. Thanks, Ubernostrum

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.