StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17149640
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-17T14:10:20.207
FavoriteCount
0
LastActivityDate
2013-06-17T14:15:46.553
LastEditDate
2013-06-17T14:15:46.553
LastEditorUserId
1325846
OwnerUserId
1325846
ParentId
17146897
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Even MongoDB doesn't support joins, you can organize data in several different ways: 1) First of all, you can inline(or embed) related documents. This case is useful, if you have some hierarchy of document, e.g. post and comments. In this case you can like so: <pre><code>{ _id: <post_id>, title: 'asdf', text: 'asdf asdf', comments: [ {<comment #1>}, {<comment #2>}, ... ] } </code></pre> In this case, all related data will be in the save document. You can fetch it by one query, but pushing new comments to post cause moving this document on disk, frequent updates will increase disk load and space usage. 2) referencing is other technique you can use: in each document, you can put special field that contains _id of parent/related object: <pre><code>{ _id: 1, type: 'post', title: 'asdf', text: 'asdf asdf' }, { _id:2 type: 'comment', text: 'yep!', parent_id: 1 } </code></pre> In this case you store posts and comments in same collection, therefor you have to store additional field type. MongoDB doesn't support constraints or any other way to check data constancy. This means that if you delete post with _id=1, comments with _id=2 store broken link in parent_id. You can separate posts from comments in different collections or even databases by using <a href="http://docs.mongodb.org/manual/reference/database-references/" rel="nofollow">database references</a>, see your driver documentation for more details. Both solutions can store tree-structured date, but in different way.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to store related records in mongodb?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USArtem Mezhenin
UserOwnerUserId
1. USArtem Mezhenin
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to store related records in mongodb?
 singulars
 PostTypePostTypeId
 PTQuestion
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.