Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The problem is more related to Java than anything else. You can't change a runtime type of an instance (at runtime), so hibernate does not provide for this kind of scenarios (unlike rails for example).</p> <p>If you want to evict the user from the session, you'll have to evict associated entities. You have some choices:</p> <ul> <li>Map the entity with evict=cascade (see the <a href="http://www.hibernate.org/hib_docs/v3/api/org/hibernate/Session.html#evict(java.lang.Object)" rel="nofollow noreferrer">Session#evict</a> javadoc)</li> <li>Manually evict all associated entites (this can be cumbersome)</li> <li>Clear the session, thus evicting all entities (of course, you'll lose the local session cache)</li> </ul> <p>I've had a similar problem in grails, and my solution is similar to <strong>grigory's</strong> solution. I copy all instance fields, including the associated entities, then delete the old entity and write the new one. If you don't have that many relations this can be easy, but if your data model is complex you'll be better off using the native sql solution you described.</p> <p>Here is the source, in case you're interested:</p> <pre><code>def convertToPacient = { withPerson(params.id) {person -&gt; def pacient = new Pacient() pacient.properties = person.properties pacient.id = null pacient.processNumber = params.processNumber def ap = new Appointment(params) pacient.addToAppointments(ap); Person.withTransaction {tx -&gt; if (pacient.validate() &amp;&amp; !pacient.hasErrors()) { //to avoid the "Found two representations of same collection" error //pacient.attachments = new HashSet(person.attachments); //pacient.memberships = new HashSet(person.memberships); def groups = person?.memberships?.collect {m -&gt; Group.get(m.group.id)} def attachs = [] person.attachments.each {a -&gt; def att = new Attachment() att.properties = a.properties attachs &lt;&lt; att } //need an in in order to add the person to a group person.delete(flush: true) pacient.save(flush: true) groups.each {g -&gt; pacient.addToGroup(g)}; attachs.each {a -&gt; pacient.addToAttachments(a)} //pacient.attachments.each {att -&gt; att.id = null; att.version = null; att.person = pacient}; if (!pacient.save()) { tx.setRollbackOnly() return } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to change Entity type in JPA?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMiguel Ping
    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
    1. COI really this this answer. First, I tried your 3rd option: clearing the session with EntityManager.clear(). This works. The problem is I'd lose any uncommited changes elsewhere in the persistence context. Now I'm tring the 1st suggestion with by adding @Cascade(value = CascadeType.EVICT) to the nested Entities causing the problem. This doesn't work, however, and I still get the same error (detached entity passed to persist). I'm putting the Hibernate tag on top of the JPA tag. This may be why.
      singulars
      1. PO
      1. USrcampbell
    2. COI also tried the 2nd option by passing the Session to the User object which would evict its child Entities, pass it to them so they could do the same, etc. down through the object graph. Nothing works. All three strategies end with the same error on the same child entity: "detached entity passed to persist"
      singulars
      1. PO
      1. USrcampbell
 

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