EF 4.3 Beta 1 on Optional Relationship the Cascade Delete leaves Orphans

Question

Is this odd?

When deleting relationships of one to many, if a the relationship is optional and you delete the parent object the rest will remain orphan and it does not cascade delete.

    var album = new Album
                {
                    Name = "Test Album",
                    Description = "Test Album Description",
                    Images = new Collection<Image>
                    {
                        new Image {
                            Name = "Image 1",
                            Description = "Image 1 Description"
                        },
                        new Image {
                            Name = "Image 2",
                            Description = "Image 2Description"
                        },
                    }
                };

            albumRepository.Add(album);
            albumRepository.UnitOfWork.Commit();

Under the Image Entity I got the AlbumId as Nullable since some images can be orphaned.

And then I call.

albumRepository.Delete(toRemove);
albumRepository.UnitOfWork.Commit();

The Album gets deleted but the images that where once related are Orphaned and their AlbumId is removed from the row.

Take a look at [How do you ensure Cascade Delete is enabled ...](http://stackoverflow.com/questions/5471374/how-do-you-ensure-cascade-delete-is-enabled-on-a-table-relationship-in-ef-code-f) — Eranga, Jan 27 '12 at 16:21

score 1 · Accepted Answer · answered Jan 27 '12 at 16:47

1

This did it.

modelBuilder.Entity<Image>()
.HasOptional(d => d.Album)
.WithMany(d => d.Images)
.WillCascadeOnDelete(true);

answered Jan 27 '12 at 16:47

Michael D. Irizarry

6,186
5
30
35

EF 4.3 Beta 1 on Optional Relationship the Cascade Delete leaves Orphans

1 Answers1