Alternate Keys in Entity Framework 7

The Discussion

• 

  Thats one code too many for something rather simple. Good work but I think using attribute would have been great or at least a simpler syntax like something in django

• 

  I use the fluent api mostly to disable cascade deletes when there are two paths between two entities. Please make the sql team lift the restriction. It's always a hassle to do the ping pong between entities, t =>, p=> t => again, p =>, finally. I never remember if I have to start from the many or the 1 side of the relation.  I would much prefer to just call a method, if maybe less 'fluently'.

• 

  @ojorma - At the moment we only have the [Key] annotation for defining primary keys... but that's a good suggestion, an [AlternateKey] annotation would be useful.

• 

  @br1 - We'll be starting work on cascade delete support shortly, so I'll keep your feedback in mind when we design it.