cascading-deletes

I have table "A" in MySQL. It has some references with cascade deleting to some other tables ("B", "C", "D" ...). I need to use a trigger when something deletes from "A". This trigger works when I delete records from "A" directly. But it doesn't work with cascade deleting. Does any version of MySQL exist where my trigger will work with cascade deleting? Or, maybe, there is another way to call Niel de Wet From http://dev.mysql.com/doc/refman/5.6/en/innodb-restrictions.html Cascaded foreign key actions do not activate triggers In other words, you cannot use the trigger with cascaded deleting.

Django models generally handle the ON DELETE CASCADE behaviour quite adequately (in a way that works on databases that don't support it natively.) However, I'm struggling to discover what is the best way to override this behaviour where it is not appropriate, in the following scenarios for example: ON DELETE RESTRICT (i.e. prevent deleting an object if it has child records) ON DELETE SET NULL (i.e. don't delete a child record, but set it's parent key to NULL instead to break the relationship) Update other related data when a record is deleted (e.g. deleting an uploaded image file) The

I have a 3 tables that look like this: (source: InsomniacGeek.com ) On the foreign keys I have set cascade deletes. Right now, when I delete a record in the Folder table, only the related record in the FolderItem is deleted. This is expected and correct. What I would to accomplish is when I delete a record in the Folder table, the corresponding records in the FolderItem and the Item table should be deleted. How do I solve this? By adding a trigger that deletes all instances of Item with the FolderID in question? Or is there any better solution? You need to decide what behavior you want exactly

I have one table that I had called equipment , and 8 other tables that I had called equipment_child1 and so on until equipment_child8 . The commom field between all that tables is cod_equip , with this field I 'm able to identify all my child equipment tables with equipment parent table. I need to delete data from equipment when the equipment is moved, but I need to delete data in all my tables equipment_child1 to equipment_child8. then I remenber I had used DELETE CASCADE in innoDB engine, but now I'm using MyISAM engina, is that a problem? Any help, will really clarify ... Yes. Simply you

I implemented a bidirectional 1:1 relationship based on this answer: Primary /Foreign Key in Entity Framework I define the bidirectional relation this way: public class Student { public virtual int StudentId { get; set; } public virtual Anamnesis Anamnesis { get; set; } . . . } public class Anamnesis { [Key, ForeignKey("Student")] public int AnamnesisId { get; set; } public virtual Student Student { get; set; } . . . } where, Student is the principal entity and Anamnesis it the entity that shares the PK. Now I'd like that the relationship created had a Delete Rule = CASCADE. Actually, the

I have problem with deleting related rows in Entity Framework 4.1. I have tables with relations Book 1<--->* BookFormats I have set the on delete cascade: ALTER TABLE [dbo].[BookFormats] WITH CHECK ADD CONSTRAINT [FK_BookFormats_Book] FOREIGN KEY([BookID]) REFERENCES [dbo].[Book] ([BookID]) on delete cascade The EDMX property Then, I want to remove the all BokFormats items related to my Book object: var originalBook = m.db.Book.First(x => x.BookID == bookId); originalBook.BookFormats.Clear(); m.db.SaveChanges(); But, I get the error: The operation failed: The relationship could not be changed

I have two entities. Profile and ProfileImages . After fetching a Profile I want to delete ProfileImages through Profile without it just removing the reference to Profile (setting it to null ). How can this be done with fluent API and Cascading Delete? Do I set the HasRequired attribute or the CascadeDelete attribute? public class Profile { //other code here for entity public virtual ICollection<ProfileImage> ProfileImages { get; set; } } public class ProfileImage { // other code here left out [Index] public string ProfileRefId { get; set; } [ForeignKey("ProfileRefId")] public virtual Profile