Bug - One to One relationship display bug


There's a display error on the relationships created by LinqPad for One to One mappings that have a non-PK Foreign Key (that is unique of course).

As you can see from the image above, Customer has a 1-1 relationship with PartyRole which is correctly displayed by LinqPad (the foreign key on customer targets the PK on PartyRole). However, it cannot do the same for the Account table. I suppose that is because the relationship is non identifying.

Sign In or Register to comment.