Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8314367
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T20:47:41+00:00 2026-06-08T20:47:41+00:00

I have the following relationships between some types A, B, C and X: A->B->X

  • 0

I have the following relationships between some types A, B, C and X:

A->B->X
|->C->X
|->X

Now assume that i want to add a new A to the database and associate it with existing instances of B, C and X.

What i’m doing is this:

using (Context context = new Context())
{
  context.As.Attach(A);
  context.As.Add(A);
  context.SaveChanges();
}

It seems to work but i’m not sure about it since Attach is usually used to attach existing instances.

This alternative does not work:

using (Context context = new Context())
{
  context.Bs.Attach(A.B);
  context.Cs.Attach(A.C);
  context.As.Add(A);
  context.SaveChanges();
}

Because in this case X gets attached twice (A.B.X and A.C.X) and entity framework throws an exception:

System.InvalidOperationException: 
An object with the same key already exists in the ObjectStateManager.
The ObjectStateManager cannot track multiple objects with the same key.

Does it make sense to use my solution or is there a better way to do this?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T20:47:44+00:00Added an answer on June 8, 2026 at 8:47 pm

    Yes your solution makes sense – you have attached whole graph and changed just A to Added state. It can be also rewritten as:

    using (Context context = new Context())
    {
      context.As.Attach(A);
      context.Entry(A).State = EntityState.Added;
      context.SaveChanges();
    }
    

    In some complex scenarios it can be also useful to do that in reverse order – add all and change state of all existing items.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Currently I have a database with the following relationships: One Client has multiple Entities
I have the following relationships set up: A HABTM B B belongsTo C C
I have three entities: Country, State and City with the following relationships: When creating
I need to create relationships for my entities, whereby I have the following scenario:
I want to know how I can find interesting relationships between users accounts such
I have a requirement to graphically depict relationships between a set of objects as
In my relationships_controller I have the following: class RelationshipsController < ApplicationController def new @user
I'm beginning work on a web application that will have several distinct user types,
I'd like to get some advice on database design. Specifically, consider the following (hypothetical)
I am looking for some, I have the following table setup in my test

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.