Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p><em>it seems like hibernate merge was not meant for associating transient objects to persistent</em></p> </blockquote> <p>Merge is JPA standard - merges "new &amp; detached entity instances" to "(persistence context-) managed entity instances". Will cascade across FK relationships marked Cascade.MERGE or Cascade.ALL.</p> <p>From a <strong>JPA</strong> perspective - no, merge was not meant for associating your Xstream streamed transient objects to persistent. JPA intends for merge to work with the normal JPA lifecycle - create new objects, persistent them, get/find them, detach them, modify them (including adding new objects), merge them, optionally modifiy them some more, then persist/save them. This is deliberate design, so that JPA is stream-lined &amp; performant - each individual object persist to the database doesn't need to be preceded with a retrieval of object state in order to determine whether/what to insert/update. The JPA persistence context object state already contains enough details to determine this.</p> <p>Your problem is that you have new entity instances that you want to act <strong><em>as if</em></strong> they have been detached - and that's not the JPA way.</p> <p>SaveOrUpdate is a hibernate proprietary operation - if an entity has an identity it is updated, but if it has not entity then it is inserted.</p> <p>From a <strong>hibernate</strong> perspective - yes, merge followed by saveOrUpdate can theoretically work for associating (Xstream streamed) transient objects to persistent, but it may have restrictions when used in conjuction with JPA operations. saveOrUpdate DOES precede each object persist to the database with a retrieve to determine whether/what to insert/update - it's smart, but it's not JPA and it's not the most performant. i.e. you should be able to get this to work with some care and the right configuration - and using hibernate operations rather than JPA operations when conflict occurs. </p> <blockquote> <p><em>I get errors such as:</em> </p> <p><em>org.hibernate.ObjectDeletedException: deleted object would be re-saved by cascade (remove deleted object from associations): [com.......SomeObject#353296]</em></p> </blockquote> <p>I believe this might be caused by two factors:</p> <ul> <li>somewhere in your (Xstream-created) object graph, a child entity instance is missing that would be present if you did a (cascaded) retrieve using JPA: this gives an object deletion</li> <li><p>somewhere else in you (Xstream-created) object graph, this same child entity is present: this gives the object being re-saved</p> <p>How to debug this: (a) create the object graph from Xstream and print it out IN FULL - every entity, every field; (b) load the same object graph via JPA, cascading the retrieve from the top entity &amp; print it out IN FULL - every entity, every field (c) compare the two - is something missing from (a) that is present in (b)??</p></li> </ul> <blockquote> <p><em>Is there any way to achieve what I want to do without having to get the persistent object in session, and modifying that, instead of modifying the transient one, and trying to save that and override the existing persistent one?</em></p> </blockquote> <p>Via the debug/fix just suggested - hopefully.</p> <p>OR my brute-force suggestion to (dumbly) side-step this bug (slows performance a little, though): after you populate IDs in the object graph, call EntityManager.clear(), THEN proceed with merge() and saveOrUpdate(). But UNIT TEST the DB results - to ensure you haven't overlooked something important in populating your Xstream graph.</p> <p>For testing / as a last resort, try the saveOrUpdate() without the merge(), but you might then be forced to clear() the Entity manager to avoid Hibernate exceptions, such as NonUniqueObjectException.</p> <p>Let me know if you learn more / have more info B^)</p>
    singulars
    1. This table or related slice is empty.
    1. POUsing Transient Entity in Hibernate to Update/Merge an existing Persistent Object
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGlen Best
    1. USGlen Best
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI've already tried to do the clear(), and the saveOrUpdate() without the merge. They yield other hibernate errors... I think such as entity copy already exists and transient object instantiation. I will give your other suggestions a try. Thank you for the thorough answer.
      singulars
      1. PO
      1. USeipark
    2. COHow would you "print" the entire object? That is essentially the original problem I was working on, which is where XStream came in.
      singulars
      1. PO
      1. USeipark
 

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