Databases
StackOverflow2013
Postsdbo
POThe DELETE statement conflicted with the SAME TABLE REFERENCE constraint with Entity Framework
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POThe DELETE statement conflicted with the SAME TABLE REFERENCE constraint with Entity Framework
    primarykey
    data
    text
    <p>I have a table with a self reference where the ParentId is an FK to the ID (PK).<br> Using EF (code-first), I've set up my relationship as follows: </p> <pre><code>this.HasOptional(t =&gt; t.ParentValue) .WithMany(t =&gt; t.ChildValues) .HasForeignKey(t =&gt; t.ParentId); </code></pre> <p>When I try to delete the children and its parent, the DELETE commands EF issues to the database are not in the order I expected them to go - it attempts to delete the parent record first. </p> <p>I realize that I have a couple of options here (neither of which I like): </p> <ol> <li>Delete child records first, do a full save/commit, and then delete parent record. With the complexity of my model and the logic that maintains it, this isn't an option - can't issue multiple commit commands whenever I want.</li> <li>Dissolve the relationship before deleting anything. This seems like a more sensible solution, but again, I have to issue separate commit with an UPDATE statement before the DELETEs. I want to avoid multiple save/commit calls.</li> <li>Use a trigger to delete children prior to deleting parent record. But I'd like to avoid triggers and their problematic nature as much as possible. </li> </ol> <p>So the question is.. is there a way to enforce the deletion of children before the parent record? Perhaps I'm missing some sort of an explicit way of telling EF that it needs to take care of these children before the parent? Maybe there's a way to direct EF to delete in a descending order of IDs? I don't know.. thoughts?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKon
    1. USKon
    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
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POThe DELETE statement conflicted with the SAME TABLE REFERENCE constraint with Entity Framework
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POThe DELETE statement conflicted with the SAME TABLE REFERENCE constraint with Entity Framework
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POThe DELETE statement conflicted with the SAME TABLE REFERENCE constraint with Entity Framework
      1. USRyu Kaplan
      1. VTBountyStart
    1. COCan you utilize a cascade delete here? If you are using code first migrations, you can set the cascade=true when the table is created, otherwise you may have to update it through another migration or via the database. I would think EF would handle it if it was able to cascade.
      singulars
      1. POThe DELETE statement conflicted with the SAME TABLE REFERENCE constraint with Entity Framework
      1. USBrad Gardner
    2. COGood idea. Our DBAs don't want to enable cascade for the whole DB, but we may be able to do it just on this FK reference. It's what I was just discussing with a DBA. :) Though I'm still looking for other suggestions/ideas perhaps within the scope of EF-related code.
      singulars
      1. POThe DELETE statement conflicted with the SAME TABLE REFERENCE constraint with Entity Framework
      1. USKon
    3. COUpdate: Unable to add cascade on delete to an FK within a self reference in a table, because of the cycle error.
      singulars
      1. POThe DELETE statement conflicted with the SAME TABLE REFERENCE constraint with Entity Framework
      1. USKon
 

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