Multiplicity conflicts with the referential constraint

c# entity-framework

Question

I'm receiving the following EF error:

Agent_MailingAddress: : Multiplicity conflicts with the referential constraint in Role 'Agent_MailingAddress_Target' in relationship 'Agent_MailingAddress'. Because all of the properties in the Dependent Role are non-nullable, multiplicity of the Principal Role must be 1

It appears to throw this when it executes base.OnModelCreating(modelBuilder).

Here are my models. FWIW, Agent inherits from a User class.

public class Agent
{
    public int AgentId { get; set; }
    public int PrimaryAddressId { get; set; }
    public Address PrimaryAddress { get; set; }
    public int? MailingAddressId { get; set; }
    public Address MailingAddress { get; set; }
}

public class Address
{
    public int AddressId { get; set; }
    public string AddressLine1 { get; set; }
    public string AddressLine2 { get; set; }
}

I believe the issue has something to do with the fact that Agent has more than one property of type Address and possibly also because one of them is nullable. I've done some searching, but can't seem to find an answer.

I assume altering my Agent model to have a single property of type List<Address> that would use a UserAddresses lookup table would resolve the error, but I would prefer to keep the current model and not.

How can I resolve this error? Thanks in advance.

1
29
9/8/2015 1:41:50 PM

Accepted Answer

This can happen if your configuration and your model do not match.

Let's say in your db configuration you have a rule like this:

protected override void OnModelCreating(DbModelBuilder modelBuilder)
{
    modelBuilder.Entity<Agent>().HasRequired(x=>x.MailingAddress);
    //..

But in your model you say that MailingAddress is optional:

public int? MailingAddressId { get; set; }

I believe the issue has something to do with the fact that Agent has more than one property of type Address and possibly also because one of them is nullable

It's not the case.

40
5/29/2017 7:57:54 AM

Popular Answer

For database first: if you altered an existing table already added to Entity Framework, say added a foreign key constraint after the fact, delete the table in the EDMX designer and add again and this will resolve the error.



Related Questions





Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow