StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14661415
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-02T11:28:15.683
FavoriteCount
0
LastActivityDate
2013-02-02T11:28:15.683
LastEditDate
LastEditorUserId
0
OwnerUserId
994168
ParentId
14655142
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Two things here. First of all you shouldn't create new entities with known IDs just to use this ID. This approach is an accident waiting to happen: an entity with this ID already exists and you will run into a <code>ConstraintViolationException</code> or <code>NonUniqueObjectException</code> because of this duplicate key. With Hibernate you can use proxies if you want to use an entity with a known ID but you do not want to select the full entity from the database. <pre><code>UserEntity user = session.load(UserEntity.class, userId); AwardEntity award = session.load(AwardEntity.class, awardId); </code></pre> This will not hit the database to select the entities but a proxy (which wraps the known id) will be returned. Within the same session you can than use the proxy like the full entity and create the new <code>RoleEntity</code> <pre><code>RoleEntity role = new RoleEntity(); role.setUser(user); role.setAward(award); session.save(role); </code></pre> The second thing is: how should Hibernate know the non-id properties of your entities without hitting the database!? The only way Hibernate could do this is using the <a href="http://docs.jboss.org/hibernate/orm/4.1/manual/en-US/html/ch20.html#performance-cache" rel="nofollow">Second Level Cache</a> (L2C), but from your question I assume that there is no L2C in place. Even though your <code>@ManyToOne</code> associations are eager-fetched Hibernate must hit the database to populate the according entities. So you may use the approach from @Bogdan's answer and re-load the role and associated user and award entities after the insert <pre><code>session.save(role); session.refresh(role); </code></pre> but this will have no performance benefit over selecting the according entities first in order to assign them to the new role <pre><code>UserEntity user = session.get(UserEntity.class, userId); AwardEntity award = session.get(AwardEntity.class, awardId); </code></pre> This will hit the database immediately and populate your entities (or return null if no row with the given ID exists). Note that when you are using proxies you can populate your entities on-demand within the same session. As soon as a non-id property is accessed the according entity is selected from the database. That said, I recommend to take a look at the Hibernate <a href="http://docs.jboss.org/hibernate/orm/4.1/manual/en-US/html/ch11.html" rel="nofollow">docs</a> for a better understanding. If you want to work with Hibernate on a production level you should also read a good Hibernate book like <a href="http://rads.stackoverflow.com/amzn/click/1932394885" rel="nofollow">Java Persistence with Hibernate</a>. Hope this helps. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POInsert with Hibernate with child objects does not return full object
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStscho
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.