Entity framework - Lazy loading based on a unique nonclustered key in a table

Question

Entity framework does not seem to lazy load related records if the key is unique and non-clustered. Just wanted to know if I am doing something wrong.

Say I have two tables - Employee and EmployeeTransactions.

EmployeeID is UNIQUE NONCLUSTERED but not the primary key of the table.

Assume for the question's sake, it is generated by another data base and inserted into the employee table.

However, most other tables have an EmployeeID which is a foreign key to table Employees

  --Table Employee 
  DBGEneratedPK
  EmployeeID (Unique NonClustered, Indexed)

  -- Table EmployeeTransactions 
  TransactionID (PK Clustered)
  EMployeeID (FK into Table A)
  Other columns

Now, when I use entity framework to retreive an employee it does not show me the option of lazy loading employeetransactions?

  employee.employeetransactions

Is this a limitation of EF?

I am just using the generated edmx. Should I do some explicit maping in the edmx? — user275157
– user275157, Commented Dec 3, 2012 at 7:44

Ladislav Mrnka · Accepted Answer · 2012-12-03 11:02:25Z

1

Yes it is limitation of EF. EF supports relations only when the key in principal table is a primary key. Just unique keys are currently not supported.

answered Dec 3, 2012 at 11:02

Ladislav Mrnka

365k60 gold badges666 silver badges673 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Entity framework - Lazy loading based on a unique nonclustered key in a table

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related