StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5909901
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-05-06T10:11:07.980
FavoriteCount
0
LastActivityDate
2011-05-06T12:32:15.540
LastEditDate
2011-05-06T12:32:15.540
LastEditorUserId
304834
OwnerUserId
304834
ParentId
2001007
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<p>The problem is that JPA, by default, will not allow proper annotations for bi-directional, shared keys, one-to-one relationships. Hibernate has the perfect construct just for that, but please mind the order properly, as well as the specific parameters to the annotations (you can also read the hibernate reference, but their example will not work unless you preset the dependent object first, which can be avoided with the method bellow - which basically saves both objects automatically, in one go). In this example, each job is processing a message. Job is the "parent" and message is the dependent object. The primary key of message will be the job id (for eliminating one extra column in the message table. You can also create an id in the message table, if you need to use message outside the job scope, using the same setup as bellow). When a job is created and a message attached, hibernate will automatically save both objects when jobDao.save is called.</p> <pre><code>@Entity @Table public class Job implements Serializable{ private Long id; @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } @OneToOne(cascade = CascadeType.ALL, mappedBy = "job") public Message getMessage() { return message; } public void setMessage(Message message) { this.message = message; message.setJob(this); } } </code></pre> <p>And now the dependent message:</p> <pre><code>@Entity @Table public abstract class Message implements Serializable { private Job job; @Id @GeneratedValue(generator = "foreign") @GenericGenerator( name = "foreign", strategy = "foreign", parameters = {@org.hibernate.annotations.Parameter(name = "property", value = "job")}) @OneToOne(optional = false, cascade = CascadeType.ALL) public Job getJob() { return job; } public void setJob(Job job) { this.job = job; } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO@PrimaryKeyJoinColumn with Bidirectional @OneToOne relationship
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBogdan Nicolau
UserOwnerUserId
1. USBogdan Nicolau
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. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
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.