1:1 relationship problems with EF Model First

Question

I'm trying to develop an application as Model-First with EF. I tried everything to accomplish a table-splitting pattern and a 1:1 relationship but looks like EF just doesn't let me.

Assuming I do use Model-First - is there a way to put a 1:1 relationship without messing with the generated files and EF giving that annoying:

Multiplicity is not valid in Role 'Blablalah' in relationship 'Blabalbala'. Because the Dependent Role properties are not the key properties, the upper bound of the multiplicity of the Dependent Role must be *.

I already tried to set my FK's as Primary Keys on destination tables but still doesn't help.

AFAIK, the only way to get EF to do 1-to-1 is to have each entity have a foreign key reference to the other entity, but I don't have a handy reference to definitively say that's true... — Tieson T., Dec 24 '12 at 01:20
You can acomplish that with code first but particularly I dont like code-first stuff. — user1695928, Dec 24 '12 at 01:22
Perhaps this helps?: http://blog.bennymichielsen.be/2011/06/02/entity-framework-4-1-one-to-one-mapping/ — Tieson T., Dec 24 '12 at 01:24

score 0 · Answer 1 · answered Dec 25 '12 at 19:25

1:1 relationship is generally defined by having foreign key in the first table and then having it cascade on delete, in database design.

IE: Users table and UserProperties table. Users table would have a UserPropertiesId as the foreign key and UserProperties would essentially treat Users as many Users to one UserProperties. That's just how things are, and if you only select by Users table it isn't an issue.

1:1 relationship problems with EF Model First

1 Answers1

Linked

Related