Ian Clelland wrote: > I would have thought that this would have been automatic -- normally > Django does a good job of telling me, when I delete an object, about > any other objects related to it which will also be deleted.
Ok, I am sorry, but I am still confused! :( First, I am using sqlite... and I checked the manage.py sqlall and it had no "on delete cascade" at all. So, is this done programmatically in python to simulate the same effect? And I had the ticket model with two foreign keys to the user record (who reported it, and who fixed it) the first one is required, while the second one is not. When I delete the user in the admin side it tells me that it will also delete all the tickes that are created by that user, but not the ones fixed by the user. So here I have a few questions: 1. Why did it do that (not that I am complaining, I just want to understand) does it have to do with one field being required and the other not? 2. Is this behavior documented anywhere? It feels a bit of magic to me when it is hard to predict how the software will behave! 3. I am still looking for an answer to my original question at the beginning of this discussion. What if I don't want to delete the tickets but assign them to another user? -- Thanks, Medhat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
