Luke Plant wrote: > On Friday 20 June 2008 23:40:43 Michael Glassford wrote: >> Django builds a list of all the objects that are foreign keyed to >> the one you are deleting and deletes those first, so it bypasses >> any ON DELETE clauses. I assume this is what you're seeing. > > Yes, this is the area I'm testing, I'm aware of how Django currently > does it (and I'm investigating a bug in Django's cascading delete). > What I'm talking about is the way that foreign key constraints > apparently are ignored inside the test harness -- did you try the > tests in the patch?
As you can see, I did not. I've only just gotten the Django unit tests running for the first time, your question seemed to be related to what I was just working on, my reply to your post was the last thing I did before stopping work for the weekend... Enough excuses. I'm usually more careful about looking closely at something before replying, and I'll try to be next time. I'm also looking at modifying Model._collect_sub_objects (to handle other types of on_delete behavior besides cascading), so no doubt I'll be looking at your changes (which you mention in another post) before long. Mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
