Navigation Property without Declaring Foreign Key

by

I believe, it is not possible to define the relationship only with data attributes. The problem is that EF’s mapping conventions assume that Creator and Modifier are the two ends of one and the same relationship but cannot determine what the principal and what the dependent of this association is. As far as I can see in the list of supported attributes there is no option to define principal and dependent end with data annotations.

Apart from that, I guess that you actually want two relationships, both with an end which isn’t exposed in the model. This means that your model is “unconventional” with respect to the mapping conventions. (I think a relationship between Creator and Modifier is actually nonsense – from a semantic viewpoint.)

So, in Fluent API, you want this:

modelBuilder.Entity<User>()
            .HasRequired(u => u.Creator)
            .WithMany();

modelBuilder.Entity<User>()
            .HasRequired(u => u.Modifier)
            .WithMany();

Because a User can be the Creator or Modifier of many other User records. Right?

If you want to create these two relationships without Fluent API and only with DataAnnotations I think you have to introduce the Many-Ends of the associations into your model, like so:

public class User
{
    public int UserId { get; set; }

    [InverseProperty("Creator")]
    public virtual ICollection<User> CreatedUsers { get; set; }
    [InverseProperty("Modifier")]
    public virtual ICollection<User> ModifiedUsers { get; set; }

    [Required]
    public virtual User Creator { get; set; }
    [Required]
    public virtual User Modifier { get; set; }
}

I assume here that Creator and Modifier are required, otherwise we can omit the [Required] attribute.

I think it’s a clear case where using the Fluent API makes a lot of sense and is better than modifying the model just to avoid Fluent configuration.

More Related Contents:

  1. Ignoring a class property in Entity Framework 4.1 Code First
  2. EF Code First: How to get random rows
  3. An error occurred while saving entities that do not expose foreign key properties for their relationships
  4. Validation failed for one or more entities. See ‘EntityValidationErrors’ property for more details [duplicate]
  5. Entity Framework Code First – two Foreign Keys from same table
  6. Decimal precision and scale in EF Code First
  7. Entity Framework Stored Procedure Table Value Parameter
  8. The entity type is not part of the model for the current context
  9. How can I automatically filter out soft deleted entities with Entity Framework?
  10. composite key as foreign key
  11. Why is .Contains slow? Most efficient way to get multiple entities by primary key?
  12. Implementing Zero Or One to Zero Or One relationship in EF Code first by Fluent API
  13. EF Code-First One-to-one relationship: Multiplicity is not valid in Role * in relationship
  14. Many-to-many mapping table
  15. One to one optional relationship using Entity Framework Fluent API
  16. Why is inserting entities in EF 4.1 so slow compared to ObjectContext?
  17. Overriding SaveChanges and setting ModifiedDate, but how do I set ModifiedBy?
  18. Does Entity Framework 4 Code First have support for identity generators like NHibernate?
  19. Entity Framework Code First Lazy Loading
  20. Entity framework code-first null foreign key
  21. How to disable cascade delete for link tables in EF code-first?
  22. Entity framework, problems updating related objects
  23. Entity Framework 4.1 InverseProperty Attribute and ForeignKey
  24. Better way to query a page of data and get total count in entity framework 4.1?
  25. Entity Framework Code First Date field creation
  26. How do I specify that a property should generate a TEXT column rather than an nvarchar(4000)
  27. Entity Framework 4.1: Unable to cast from DbQuery to ObjectQuery
  28. mapping multiple tables to a single entity class in entity framework
  29. Entity Framework: field of composite key cannot be nullable?
  30. Create association on non-primary key fields with Entity Framework 4.1 Fluent API

Leave a Comment