StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10270220
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-04-22T17:23:19.487
FavoriteCount
0
LastActivityDate
2012-04-22T17:23:19.487
LastEditDate
LastEditorUserId
0
OwnerUserId
421049
ParentId
10166656
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
This may be the answer; I'll have to wait several days to see if it indeed fixes the problem. There are actually two parts. First, for full disclosure, my <code>NewBar</code> class was actually a subclass of <code>AbstractBar</code>. I eventually wanted to have different type of embeddable bars, so I placed <code>@Embeddable</code> at the <code>AbstractBar</code> level, not at the <code>NewBar</code> level, and placed the private <code>foobar</code> field at the <code>AbstractBar</code> level as well. The funny thing is, this worked some of the time. And as I mentioned, sometimes I would come back the next day and Hibernate wouldn't load the <code>foobar</code> field. I don't understand why it didn't either work all the time or work none of the time. Secondly, when I tried to get rid of this hierarchy so as to eliminate one source of the problem, I conflated <code>AbstractBar</code> and <code>NewBar</code> but forgot to bring the <code>@Embeddable</code> up from <code>AbstractBar</code> to <code>NewBar</code>, so Hibernate didn't see that was an embeddable class, and didn't know how to load a string into a <code>NewBar</code> field without an <code>@Embeddable</code> designation. This is why <code>OtherBar</code> (with an <code>@Embeddable</code> annotation) worked, but not <code>NewBar</code> (with no <code>@Embeddable</code> annotation). This much I understand. Why Hibernate didn't warn me that it couldn't figure out how to load a field, I don't know. So to summarize, Hibernate won't load an embeddable field if you've left the <code>@Embeddable</code> annotation off the class. As for the original problem, I can only guess that <code>@Embeddable</code> is flaky when trying to use it on a class hierarchy, and that you're best off keeping all your embeddable fields at one level in the embeddable class. I hope that's the issue. We'll see if it continues to work tomorrow.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHibernate swap out embeddable class for migrating existing data
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGarret Wilson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHibernate swap out embeddable class for migrating existing data
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.