StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4152854
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-11T09:17:28.383
FavoriteCount
0
LastActivityDate
2010-11-11T09:17:28.383
LastEditDate
2017-05-23T11:47:40.267
LastEditorUserId
-1
OwnerUserId
70604
ParentId
4143597
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> I have @OnDelete annotation on all the @OneToMany members. What would be the order of deletion of these objects when the parent object is removed. Is it safe to assume that it would be the order in which the objects are declared. </blockquote> So you are using a SQL cascade delete on deletion instead of the regular Hibernate mechanism. Since you're using a database mechanism, I'm tempted to say the order in which the objects are declared does not matter (the database is simply not aware of this order) and I would just expect the database to handle things appropriately. It might influence the order of columns if you are generating the model from annotations though but: <ul> <li>I'd be very surprised if this had any impact, that would make everything extremely fragile, unusable.</li> <li>Hibernate/JPA doesn't say anything about the order of columns (because this shouldn't matter, see above).</li> </ul> <blockquote> But I ran into few issues, if B inturn has a foreign key reference to A which causes A to fail on deletion </blockquote> You should mention that in the question, this is very relevant IMO. Take my answer with a grain of salt but as I said, I'd expect a database engine to handle things appropriately, a database engine has all the required metadata to do it. But I'm not a database expert, I'm not sure what the theory says. Maybe have a look at questions such as: <ul> <li><a href="https://stackoverflow.com/questions/1637708/what-is-the-problem-with-foreign-key-cascade-multiple-paths-and-cycles">What is the problem with foreign key cascade multiple paths and cycles?</a> </li> <li><a href="https://stackoverflow.com/questions/60168/in-what-order-are-on-delete-cascade-constraints-processed">In what order are ON DELETE CASCADE constraints processed?</a></li> <li>etc etc etc</li> </ul> Or ask a question about the theory (and the practice for a given engine).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODeletion order for contained @OneToMany members
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USPascal Thivent
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
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.