StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17462949
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-07-04T06:05:44.477
FavoriteCount
0
LastActivityDate
2013-07-04T06:05:44.477
LastEditDate
LastEditorUserId
0
OwnerUserId
1615501
ParentId
16940818
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> Is there a way I could add the object to the session, and it would be marked as persistent, but not call save() (that is, the INSERT will not be generated) until the very end? </blockquote> Consider re-factoring to use <code>Session.persist(Object)</code> instead of <code>Session.save(Object)</code> if you want to defer the execution of <code>INSERT</code> until the session is flushed and/or the transaction is closed. From section 10.2 of the <a href="http://docs.jboss.org/hibernate/orm/3.3/reference/en-US/html/objectstate.html#objectstate-makingpersistent" rel="nofollow">JBoss Hibernate Community documentation</a>: <blockquote> You can also use persist() instead of save(), with the semantics defined in the EJB3 early draft. <ul> <li><code>persist()</code> makes a transient instance persistent. However, it does not guarantee that the identifier value will be assigned to the persistent instance immediately, the assignment might happen at flush time. <code>persist()</code> also guarantees that it will not execute an <code>INSERT</code> statement if it is called outside of transaction boundaries. This is useful in long running conversations with an extended Session/persistence context.</li> <li><code>save()</code> does guarantee to return an identifier. If an <code>INSERT</code> has to be executed to get the identifier ( e.g. "identity" generator, not "sequence"), this <code>INSERT</code> happens immediately, no matter if you are inside or outside of a transaction. This is problematic in a long-running conversation with an extended Session/persistence context.</li> </ul> </blockquote> Another useful reference can be found in the top-left cell of the method-to-scenario grid at the top of the "Putting it All Together" section of this <a href="http://blog.xebia.com/2009/03/23/jpa-implementation-patterns-saving-detached-entities/" rel="nofollow">blog article</a> that describes the behavior of <code>persist()</code> on objects that have never been persisted as follows: <blockquote> <ol> <li>Object added to persistence context as new entity</li> <li>New entity inserted into database at <code>flush()</code>/<code>commit()</code></li> </ol> </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMake hibernate save() and update() as a single insert optimization
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJohn Heinnickel
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.