Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can structure mongo documents just like you would in a relational database, for example, having separate collections for creditors and owners and using carpool_debts as a link table with the amount attached:</p> <pre><code>carpool_debts{ _id, owner_id, creditor_id, amount} creditors{ _id, name} owners{ _id, name} </code></pre> <p>However, this is not using mongodb to its full potential. Especially if this is a database with masses of data, you may want to optimise it for the most used queries, otherwise it'll be slow. For example, to optimise for looking up an owner's debt, you can add the data needed right there in the owners collection, using sub documents for creditors, and sub documents again for individual debts, similar to what you've already done:</p> <pre><code>owners{ _id, name, creditors: {id, name, debts: { amount, due_date} } } </code></pre> <p>and similarly, add the debt information on the creditors collection if you often look up the outstanding debt of creditors:</p> <pre><code>creditors{ _id, name, debtors: { owner_id, owner_name, debts: { aount, due_date } } } </code></pre> <p>This way, you only need to look up one record to get all the information you need. Of course, there are catches. First of all, this is not very DRY, but that's intentional. But you have to remember to update the other table(s) when something changes. If you change the name of a creditor for example, you'll need to update every owner document that has debts with this creditor (make sure you index that). This of course makes updates much slower (and the database bigger), but if you don't update very often, and look up much more often, this is not going to be a problem. Also if for example creditors can have thousands of individual outstanding debts, you may have to separate that into a link table, or rather, link collection, like this, so you don't exceed mongodb's maximum document size:</p> <pre><code>creditors{ _id, name, } debtors: { owner_id, creditor_id, debts: { amount, due_date } } </code></pre> <p>Then you have one document for each creditor-owner connection. This means more documents to look up when looking at a creditor, but still just one for looking up an owner.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is a good way to handle "complex" mongodb documents in meteor
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRonny Ager-Wick
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat is a good way to handle "complex" mongodb documents in meteor
      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. VTAcceptedByOriginator
    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. COThanks for the explanation of my options and each pro and con.
      singulars
      1. PO
      1. USshinank
 

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