Databases
StackOverflow2013
Postsdbo
POJPA Delete with 2 Interlocking Entity Classes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJPA Delete with 2 Interlocking Entity Classes
    primarykey
    data
    text
    <p>I have 2 EJB 3 Entity Beans:</p> <pre><code>@Entity public class Organisation { @Id @Column(length = 64) private String guid; private String name; @ManyToOne(fetch = FetchType.LAZY, cascade = CascadeType.REMOVE) @JoinColumn(name = "home_unit_fk", nullable = true) private Unit homeUnit; } @Entity public class Unit { @Id @Column(length = 64) private String guid; private String name; @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "organisation_fk", nullable = false) private Organisation organisation; @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "parent_unit_fk", nullable = true) private Unit parentUnit; @OneToMany(mappedBy = "parentUnit", fetch = FetchType.LAZY, cascade = CascadeType.REMOVE) @OrderBy("shortName") @OptimisticLock(excluded = true) private Set&lt;Unit&gt; childUnits; } </code></pre> <p>If I do a delete on the Organisation using standard Dao :</p> <pre><code>public int deleteByGuid(final String guid) { final Query query = entityManager.createQuery("delete from " + getPersistentClass().getName() + " where guid = :guid"); query.setParameter("guid", guid); return query.executeUpdate(); } </code></pre> <p>But I get the following exception:</p> <p>com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (<code>config</code>.<code>unit</code>, CONSTRAINT <code>FK27D184F5D4393D</code> FOREIGN KEY (<code>organisation_fk</code>) REFERENCES <code>organisation</code> (<code>guid</code>))</p> <p>I don't get it. What am I doing wrong? Shouldn't JPA/Hibernate perform deletes on both the Unit and the Organisation within the same transaction?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USTiGz
    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. POJPA Delete with 2 Interlocking Entity Classes
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJPA Delete with 2 Interlocking Entity Classes
      1. USkazanaki
      1. VTFavorite
    1. This table or related slice is empty.
 

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