Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If You need to query on your Users, keep users alone. If You need to query on your uploads, keep uploads alone.</p> <p>Another question you should ask yourself is: Every time i need this data, do I need the embedded objects (and vice-versa)? How many time this data will be updated? How many times this data will be read?</p> <p><strong>Think about a friendship request:</strong> Each time you need the request you need the user which made the request, then embed the request inside the user document.</p> <p>You will be able to create an index on the embedded object too, and your search will be mono query / fast / consistent.</p> <hr> <p><em>Just a link to my previous reply on a similar question:</em> <a href="https://stackoverflow.com/questions/3128200/mongo-db-relations-between-objects/7287321#7287321">Mongo DB relations between objects</a></p> <p>I think this post will be right for you <a href="http://www.mongodb.org/display/DOCS/Schema+Design" rel="nofollow noreferrer">http://www.mongodb.org/display/DOCS/Schema+Design</a></p> <p><strong>Use Cases</strong></p> <p><em>Customer / Order / Order Line-Item</em></p> <blockquote> <p>Orders should be a collection. customers a collection. line-items should be an array of line-items embedded in the order object.</p> </blockquote> <p><em>Blogging system.</em></p> <blockquote> <p>Posts should be a collection. post author might be a separate collection, or simply a field within posts if only an email address. comments should be embedded objects within a post for performance.</p> </blockquote> <p><strong>Schema Design Basics</strong></p> <p><em>Kyle Banker, 10gen</em></p> <blockquote> <p><a href="http://www.10gen.com/presentation/mongosf2011/schemabasics" rel="nofollow noreferrer">http://www.10gen.com/presentation/mongosf2011/schemabasics</a></p> </blockquote> <p><em>Indexing &amp; Query Optimization Alvin Richards, Senior Director of Enterprise Engineering</em></p> <blockquote> <p><a href="http://www.10gen.com/presentation/mongosf-2011/mongodb-indexing-query-optimization" rel="nofollow noreferrer">http://www.10gen.com/presentation/mongosf-2011/mongodb-indexing-query-optimization</a></p> </blockquote> <p>**These 2 videos are the bests on mongoddb ever seen imho*</p>
    singulars
    1. This table or related slice is empty.
    1. POMongoose: populate() / DBref or data duplication?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USkilianc
    1. USkilianc
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMongoose: populate() / DBref or data duplication?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo how does one go about updating the duplicate date? In the blogging example if we are duplicating come of the users information (eg. name) in the comment record for quick mono quieries. If that user changes their name we need to update every instance of their name across the database, in this case every comment they have made.
      singulars
      1. PO
      1. USwilsonpage
    2. COyou need to ask yourself, how many times do you will change your username? maybe a mass update will make at you case, or simply make an ObjectId to the user document. Object embedding is an option, not an mongodb dojo.
      singulars
      1. PO
      1. USkilianc
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload