StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20409312
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-05T19:53:31.820
FavoriteCount
0
LastActivityDate
2013-12-05T19:53:31.820
LastEditDate
LastEditorUserId
0
OwnerUserId
1913500
ParentId
13950064
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I've been looking all day for a solution to this problem. I have a solution / work around. <pre><code>@OneToMany(fetch = FetchType.LAZY,cascade = CascadeType.ALL, orphanRemoval=true ) @JoinColumn(name="PROJECT_ID", nullable=true) private Set<Person> personlist = new HashSet<Person>(); </code></pre> I have a similar issue regarding foods and ingredients. A food can exist without being an ingredient in a recipe. An ingredient can't exist without being a food. So we have a one to zero or many between ingredient and food: RECIPE 1 ------------- 1..* INGREDIENT 0..* --------- 1 FOOD Please excuse the rubbish representation above. I hope you get the idea. When fetch type below is EAGER, I get the same issue as you. when it's set to lazy, I don't. <pre><code>@NotFound(action = NotFoundAction.IGNORE) @OneToMany(mappedBy = "food", // the VARIABLE NAME of this class in Ingredient targetEntity = Ingredient.class, // The type that we have many of fetch = FetchType.LAZY, cascade = CascadeType.ALL) private Set<Ingredient> ingredients; </code></pre> This isn't really a good solution, just a work around. I think an EAGER fetch should fetch without error even if there's nothing to fetch, then I'd have foods available and if they happen to be ingredients in recipes, then I'd have those ingredients availabel in my object, and through that, the recipes they are in. If they are not ingredients, just foods on their own, I still want the foods - it's just they'll have no ingredients associated no problem... but can't have them if this is the only work around Does anyone have any better solutions to this? If you do you could save my life here :-)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POorg.hibernate.AssertionFailure: null identifier with OneToMany/ManyToOne Relationship
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USrossagator
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.