StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13809846
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-12-10T21:48:43.383
FavoriteCount
0
LastActivityDate
2012-12-10T21:48:43.383
LastEditDate
LastEditorUserId
0
OwnerUserId
571407
ParentId
11049673
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
If <code>Container</code> has a bidirectional OneToOne with <code>SomeTypeOfContainerAssignment</code>, which extends <code>ContainerAssignment</code>, then the container field should not be defined and mapped in <code>ContainerAssignment</code>, but in <code>SomeTypeOfContainerAssignment</code>: <pre><code>public class Container { @Id private Long id; @OneToOne(mappedBy = "container") private SomeTypeOfContainerAssignment someTypeOfContainerAssignment; } public class ContainerAssignment { @Id private Long id; } public class SomeTypeOfContainerAssignment extends ContainerAssignment { @OneToOne private Container container; } </code></pre> If all the types of container assignments have such a OneToOne association with COntainer, you can define the Container as <pre><code>public abstract class ContainerAssignment { @Id private Long id; public abstract Container getContainer(); public abstract void setContainer(Container container); } </code></pre> To be honest, I don't know if you're allowed to use the same join column in the table to map the <code>@OneToOne container</code> fields of each subclass. I think this is the best you can have. If you put the container field in the base class, then you must define the association as a OneToMany/ManyToOne association, since it's what it really is. I don't think what you want to do is possible, and I wouldn't mess with composite PKs, as they're discouraged for good reasons, and a nightmare to use.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODiscriminatorColumn as part of primary key / id
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJB Nizet
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. COThanks for your answer, but it doesn't really solve the question - is there a way to put the `DiscriminatorColumn` kinda inside the PK? I agree that an artificial PK is the best choice, but in many systems we can't control the schema and have to deal with composite PKs.
 singulars
 PostPostId
 PO
 UserUserId
 USBruno Kim

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.