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 135281
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 11, 20262026-05-11T06:45:54+00:00 2026-05-11T06:45:54+00:00

Entity Framework magically interprets the following table structure as a many-to-many relationship. table foo

  • 0

Entity Framework magically interprets the following table structure as a many-to-many relationship.

table foo (int id) table foo_bar (int foo_id, int bar_id) table bar (int id) 

But if the join table has any additional fields it will instead be interpreted as two one-to-many relationships.

I am using a database in which the join table has a surrogate key as primary key. Because of this EF interprets it as two one-to-many relationships.

table foo (int id) table foo_bar (int surrogate_pk, int foo_id, int bar_id) table bar (int id) 

Is it possible to modify EF:s interpretation to make it an actual many-to-many relationship in the model? Can it be done using the designer?

  • 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. 2026-05-11T06:45:55+00:00Added an answer on May 11, 2026 at 6:45 am

    I am positive that this cannot be done using the designer. I don’t know if there is a way to do it in EDMX manually, but I have never seen an example of it. One possible workaround might be to not map the surrogate key at all. If you can generate that on the database, you might not need it in your model.

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

Sidebar

Ask A Question

Stats

  • Questions 203k
  • Answers 203k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer I really think that "learning Flex" is a mistake. Focusing… May 12, 2026 at 8:33 pm
  • Editorial Team
    Editorial Team added an answer Try changing the line: if ($prof->id == $prof->id) to if… May 12, 2026 at 8:33 pm
  • Editorial Team
    Editorial Team added an answer There is a problem because it is a macro, and… May 12, 2026 at 8:33 pm

Related Questions

I need to load a model, existing of +/- 20 tables from the database
Entity framework provides great flexibility to update data in the same datacontext Dim personA
Entity framework is cripplingly slow so I tried using a stored procedure but I
The Entity Framework does not support the Expression.Invoke operator. You receive the following exception

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

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.