id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
7360	Documentation should be clearer about when save and delete are called.	Richard Bell <rbell01824@…>	nobody	"An hour later I know what caused the behavior and it seems to me to be a Django bug or at least deficiency.

This behavior occurred during an initialization of the application.

First the table xx_xxnode was initialized by deleting all of its records and then reloading the table from an external source.  It has a character field primary key.

Then the table xx_xxraid needs to be initialized.  xx_xxraid has a foreign key to the table xx_xxnode.  However, when xx_xxnode's records were deleted, Django also deleted the linked records in xx_xxraid since the keys were no longer valid.  All of which is OK and if I read the documents closely is in fact documented.

However, there is a problem.  The model for xx_xxraid overrides the delete method.  While the records in xx_xxraid are in fact being deleted as an (appropriate) side effect of the delete of xx_node's records the delete method of xx_xxraid is NOT being invoked.  It seems likely that add and delete are overrides associated with the admin interface NOT, sadly, with the DB API.

No joy, but at least I know what is going on. "		closed	Documentation	dev		duplicate			Unreviewed	0	0	0	0	0	0