StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19441189
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-18T03:40:22.623
FavoriteCount
0
LastActivityDate
2013-10-18T03:40:22.623
LastEditDate
2017-05-23T11:52:50.163
LastEditorUserId
-1
OwnerUserId
2889388
ParentId
18739755
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I encountered the same problem. And I tried 4 ways to walk around this problem. All work. <pre><code> 1. change merge(User) to saveOrUpdate(User) 2. After merge, call session.clear() 3. Use a new session for the second merge 4. User = merge(User) </code></pre> <hr> Then I did some research wondering what make these solutions possible. Note the 2nd solution. According to <a href="https://stackoverflow.com/questions/8118436/org-hibernate-session-clear-considered-harmful">org.hibernate.Session.clear() considered Harmful?</a> <code>clear</code> clears the L1 cache. So I believe after you merge, somehow data is still stored in cache. <code>Clear</code> will detach all the objects associated with this session. Note 1st solution. According to this <a href="https://stackoverflow.com/questions/5311928/hibernate-envers-merge-saveorupdate">hibernate envers: merge & saveOrUpdate</a> difference between <code>saveOrUpdate</code> and <code>merge</code> is that <code>saveOrUpdate</code> makes the object persistent, whereas <code>merge</code> return the persistent object. When you merge again, since the argument is not persistent, hibernate uses the cache to load object from db. This results in the strange query. So I came to the 4th solution. This makes your user the attached object. Then when you merge again, it is merging the persistent object. Hibernate doesn't query db this time. As for the 3rd solution. It came from a trial. These are my understanding for this question. Not sure if it's accurate. But I hope this helps. To be safe, I recommend you use <code>solution 1</code>, and <code>solution 4</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHibernate 4 merge detached Object twice
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USProbableMax
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHibernate 4 merge detached Object twice
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
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.