Hi - In this example we have created a seperate table, the relationship is between the 'Blog' and the 'image' table. Then the 'BlogImage' table which connects the two allows any Blog to be related to multiple Images and any Image to be related to multiple blogs. If I've misunderstood your question please let me know - happy to help!
@@iseesharp7475 Oh sorry, might have missed it. Is there any way you could review my entity design? I have started learning EF and as far as I have seen. We can just do ICollection on 2 entities to have many to many relationship. But by SQL standard we must create another joining table. I don't know which one is best, or it's about use cases.
The BlogImage table was created automatically by entity framework when we defined a many to many relationship between the Blog class and Image class using the navigation properties.
@@iseesharp7475 uh huh. This is what I read in EF docs, that EF automatically created joining tables. Right? I was confused because it didn't create for me. I will just have to debug my way through it I guess. Thanks for taking the time sir. You are the best, loving the community
@@nokibulislam9423 Yeah as long as you have the ICollection in Blog and Image the join table should be created for you. Fell free to send me a github repo or pastbin if you need help. Thanks for the kind words!
