StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15055338
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-24T18:55:09.073
FavoriteCount
0
LastActivityDate
2013-02-24T19:00:14.763
LastEditDate
2013-02-24T19:00:14.763
LastEditorUserId
11092
OwnerUserId
11092
ParentId
15051640
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I will give some hints but you need to dig into source code and documentation.There are lot of concepts here. Doing some operation on session does not mean that the changes are immediately pushed to db. This depends a lot on the flush mode of the session and operation you are doing. Refer to hibernate documentation on this. Changes are pushed to db when session is flushed. The changes are durable once transaction is committed. It would have worked if you called <code>session.flush()</code> before close, in the commented code but it is unnecessary because of explanation below. In the above code for update and delete, when call 'getCurrentSession', you either get the existing session or get the new session from <code>org.springframework.orm.hibernate4.SpringJtaSessionContext</code>(assuming you are using JTA, again dig into code to understand this). When new session is created Hibernate register synchronization with the transaction. Before complete of the transaction Hibernate will get call back. Here Hibernate will flush the session. In your case the transactions demarcated by spring through the annotations you placed. I advice you to debug the code from call to 'getCurrentSession' in order t understand what is happening. You will come across these classes/methods depending on your configuration. <pre><code> org.hibernate.internal.SessionFactoryImpl.getCurrentSession() org.springframework.orm.hibernate4.SpringJtaSessionContext.buildOrObtainSession() org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorImpl.beforeCompletion() </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSome doubts about delete and updating table row using Hibernate in Spring application
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAdi
UserOwnerUserId
1. USAdi
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.