Databases
StackOverflow2013
Postsdbo
POOne-To-One relationship with fluent api. A Hacky way?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOne-To-One relationship with fluent api. A Hacky way?
    primarykey
    data
    text
    <p>EF 4.3.1. I have defined <code>User</code> and <code>Box</code> entities. Each box may or may not be assigned to a user.<br> What I'd like to achieve is to have a <code>OwnBox</code> property in <code>User</code> class, and an <code>Owner</code> property in <code>Box</code> class.<br> in Database, I have defined <code>OwnerId</code> foreignkey in <code>Boxes</code> (<code>Boxes.OwnerId</code> has relation with <code>Users.UserId</code>).<br> To define the relationship with fluent api, I have defined the following classes: </p> <pre><code>public partial class User { public int UserId {get; set;} public virtual Box OwnBox { get; set; } } public partial class Box { public int? OwnerId { get; set; } public virtual User User { get; set; } } </code></pre> <p>Then in my Mapping class for <code>Box</code>, I have defined the relations as follows: </p> <pre><code>this.HasOptional(t =&gt; t.User).WithOptionalDependent(d =&gt; d.OwnBox). Map(m =&gt; m.MapKey("OwnerId")).WillCascadeOnDelete(true); </code></pre> <p>But by firing up the project, I got the error: </p> <blockquote> <p>Schema specified is not valid. Errors: (56,6) : error 0019: Each property name in a type must be unique. Property name 'OwnerId' was already defined.</p> </blockquote> <p>So I had to tell EF to forget about the <code>OwnerId</code> column first: </p> <pre><code>this.Ignore(t =&gt; t.OwnerId); </code></pre> <p>Now the project works fine. But I'm still doubtful if this is a good approach and will everything work fine on CRUD operations with foreign key associations. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCodingGorilla
    1. USKamyar
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOne-To-One relationship with fluent api. A Hacky way?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POOne-To-One relationship with fluent api. A Hacky way?
      1. USMariusz.W
      1. VTFavorite
    1. COHave you tried removing the mapping and just letting EF figure out what you mean?
      singulars
      1. POOne-To-One relationship with fluent api. A Hacky way?
      1. USCodingGorilla
    2. COSince I'd like to have a one-to-one relationship, and I'm not following conventions, I'm pretty sure it's not gonna work.
      singulars
      1. POOne-To-One relationship with fluent api. A Hacky way?
      1. USKamyar
    3. COI'm fairly certain the reason why you're getting that is because of the `Map` call.
      singulars
      1. POOne-To-One relationship with fluent api. A Hacky way?
      1. USMike Bailey
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload