Configuring non standard foreign keys

Question

Hi all,
I am sure this is very easy, but I can't get it to work & would appreciate some guidance. Basically, I have two classes similar to the following:
Partial Public Class ShoeRecord
   Public Property Id as integer
   Public Property size as string
   Public Property ShoeLaceColour as string
End Class
..... and also.....
Partial Public Class ShoeSet
   Public Property Id as Integer
   Public Property LeftShoeId as Integer
   Public Property RightShoeId as Integer
End Class
Everything runs okay with it set up as-is, but then I tried to change  ShoeSet as follows.......
Partial Public Class ShoeSet
   Public Property Id as Integer
   Public Property LeftShoeId as Integer
   Public Property leftShoe as ShoeRecord
   Public Property RightShoeId as Integer
   Public Property RightShoe as ShoeRecord
End Class
When I try to migrate, I get the following error:
 "Error Number:1785,State:0,Class:16
Introducing FOREIGN KEY constraint 'FK_dbo.ShoeSets_dbo.ShoeRecords_LeftShoeId' on table 'ShoeSets' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.
Could not create constraint. See previous errors."
I have been trying to use fluent API to configure the relationship between keys LeftShoeId and ShoeRecord.Id, but can't seem to get it working. Can anyone help?
Thanks.

Answer 1

Hello,
Please have a try to set the WillCascadeOnDelete with a false flag as:
modelBuilder.Entity<ShoeSet>().HasRequired(s => s.leftShoe).WithMany().HasForeignKey(s=>s.LeftShoeId).WillCascadeOnDelete(false);
modelBuilder.Entity<ShoeSet>().HasRequired(s => s.RightShoe).WithMany().HasForeignKey(s => s.RightShoeId).WillCascadeOnDelete(false);
As the exception already describes that there is a cycle reference in the current model, setting the WillCascadeOnDelete with a false flag will specify the ON DELETE NO ACTION or ON UPDATE NO ACTION.
If you need to know more about this issue, please refer to this link:
Introducing FOREIGN KEY constraint may cause cycles or multiple cascade paths
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.