Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The question here seems like it could be abstracted from "where should I store my roles" to "how should I store related information in Mongo (or NoSQL in general)". It's a relation vs non-relational modeling issue. </p> <p><strong>Non-Relational</strong></p> <p>Using Node + Mongo, storing the roles on the user will make it really easy to determine if a user has access to the feature, given that you can just look in the 'roles' property. The trade off is that you have lots of duplicate information ('user_read' could be a role on <em>every</em> user account) and if you end up changing that property, you'll need to update it inside <em>every</em> user object. </p> <p>You could store the roles in their own collection and then store the id for that entry in the Roles collection on your User model, but then you'll still need to fetch the actual record from the collection to display any of it's information (though arguably this could be a rare occurrence)</p> <p><strong>Relational</strong></p> <p>Storing these in a relational DB would be a more "traditional" approach in that you can establish the relationships between the tables (via FKs / join tables or what not). This <em>can</em> be a good solution, but then you no longer have the benefits of using a NoSQL database. </p> <p><strong>Summary</strong> </p> <p>If the rest of your app is stored in Mongo and <strong>has</strong> to stay there (for performance or whatever constraint) then you are probably better off doing it all in Mongo. Most of the advice I've come across says don't mix &amp; match data stores, e.g. use one or the other, but not both. That being said, I've done projects with both and it can get messy but sometimes the pros outweigh the cons.</p>
    singulars
    1. This table or related slice is empty.
    1. POACL best practices, store roles in user object, or separate table/collection?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDavid Welch
    1. USDavid Welch
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POACL best practices, store roles in user object, or separate table/collection?
      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. COI'm dying to know the rest of the summary! :)
      singulars
      1. PO
      1. USaz_
    2. COHaha thanks. Must have lost focus and not realized. I tend to trail off like that when I speak too ;)
      singulars
      1. PO
      1. USDavid Welch
    3. CO@DavidWelch, in general what you say makes sense, but there are times that relational "style" makes sense in the context of NoSQL. For example, what if I am in Mongo (or Couch or whatever), and I have these big user objects that are updated infrequently, but roles are updated frequently. Even in NoSQL, wouldn't it make sense to have a separate collection for the roles, so you can access them atomically, without constantly updating the user?
      singulars
      1. PO
      1. USdeitch
 

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