cascading-deletes

I'm reasonably new to EF, and struggling a little to facilitate deleting my objects. My two objects and associated DbContext look as follows: public class Context: DbContext { public Context() : base(){} public DbSet<Person> Persons {get;set;} public DbSet<Vehicle> Vehicles {get;set;} } public class Person { public int PersonID {get;set;} public string Name {get;set;} } public class Vehicle { public int VehicleID {get;set;} public int? PersonID {get;set;} [ForeignKey("PersonID")] public virtual Person Person {get;set;} } As per above, one person can be linked to multiple vehicles. There is no

I am using EF4 CTP 5, CodeFirst. Please see my classes first: public class Guest { [Key] public Guid GuestID { get; set; } public Language PreferredLanguage { get; set; } public Guid? LanguageID { get; set; } } public class Language { [Key] public Guid LanguageID { get; set; } [Required(ErrorMessage = "Enter language name")] [StringLength(50, ErrorMessage = "Language name is too long")] public string LanguageName { get; set; } // in origine language } My goal is to set a certain "Delete Rule" for the Guest-Language relationship. When a language is deleted, I do not want to delete the

What is the difference between the 2 options above? When is it preferable to choose each option? Serge Kvashnin The basic difference between them is: When using the orphanRemoval=true option Doctrine makes the assumption that the entities are privately owned and will NOT be reused by other entities. If you neglect this assumption your entities will get deleted by Doctrine even if you assigned the orphaned entity to another one. Say your User has one-to-many relation to Comment . If you are using cascade="remove" , you can remove the reference for Comment from one User , and then attach that

Using the following related models (one blog entry can have multiple revisions): class BlogEntryRevision(models.Model): revisionNumber = models.IntegerField() title = models.CharField(max_length = 120) text = models.TextField() [...] class BlogEntry(models.Model): revisions = models.ManyToManyField(BlogEntryRevision) [...] How can I tell Django to delete all related BlogEntryRevision s when the corresponding BlogEntry is deleted? The default seems to be to keep objects in a many-to-many relation if an object of the "other" side is deleted. Any way to do this - preferably without overriding

Howdy, I have a problem where i need a cascade on multiple foreign keys pointing to the same table.. [Insights] | ID | Title | | 1 | Monty Python | | 2 | Spamalot | [BroaderInsights_Insights] | broaderinsight_id | insight_id | | 1 | 2 | Basically when either record one or two in the insights table is deleted i need the relationship to also be deleted.. I've tried this: CREATE TABLE broader_insights_insights(id INT NOT NULL IDENTITY(1,1), broader_insight_id INT NOT NULL REFERENCES insights(id) ON DELETE CASCADE, insight_id INT NOT NULL REFERENCES insights(id) ON DELETE CASCADE, PRIMARY KEY(id))

I have a table representing users. When a user is deleted I get: DELETE statement conflicted with the REFERENCE constraint Apparently, CASCADE DELETE is not as easy as I imagined in SQL Server, and the option needs to be added to the table. The problem is: I cannot figure out how to add the CASCADE DELETE option. I'm using: SQL Server 2008 . Any ideas how to do this? Read this Microsoft article first. Read Me . I use the GUI during design so here is a picture of how it is selected in SSMS. The syntax added to the foreign key is " ON DELETE CASCADE " Mr. TA Google ALTER TABLE DROP CONSTRAINT ,