Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Initially i suggest to create only UserDocument and embed all event related collection inside of user, in the future you will see if events will be big collection(more that mongodb limit 4mb) you will move it into separate collection. As for images look at mongodb <a href="http://www.mongodb.org/display/DOCS/GridFS+Specification" rel="nofollow">gridFs</a> feature, it allow you to store file with any size. In user document you could store only collection of fileId.</p> <p>When you start to design document databe schema always start from embedding evething, later you will see what you need move into separate collection. In you case if you will need for example show list of all events you can't do it easy, because you need to load each user and get embeded collection of events, in such situation need to move events in separate collection.</p> <p><strong>Update:</strong></p> <p>Because you need to refernce to the event from any user document, you need to move event into separate collection, because it's always bad to reference to the embedded collections.</p> <p>So after disscussions with myself, seems to me that following scheme should fit you need:</p> <pre><code>UserDocument Collection -UserId -Type -Details -Events(EventId) -AppliedEvents -AttendingEvents -Files(it's not actual files it just references to gridFs filess) EventDocument Collection -EventId -EventDetail -FollowingUsers </code></pre> <p>I've moved almost all into UserDocument, because User is a 'strong' entity and you will work with user more than with event(it seems so for me).</p>
    singulars
    1. This table or related slice is empty.
    1. POBasic mongodb theory
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAndrew Orsich
    1. USAndrew Orsich
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, this also seems like a good solution. Can I ask why followingusers is in the event document and applied and ettending is in user document? - Thanks for clarifying how files would work!
      singulars
      1. PO
      1. This table or related slice is empty.
    2. CO@Colin: Following users in event document because i suppose that you need show event and users that follow the event(it easy task if following user inside of event), but for the applied events i suppose you shoud show user and his applied events(it's easy when applied events inside of user).
      singulars
      1. PO
      1. USAndrew Orsich
    3. COthe mongodb limit of 4MB (was raised to 16MB) is for documents, not collections. And 16MB is way too big to worry about it unless you store several novels inside one document.
      singulars
      1. PO
      1. USSalvatorelab
 

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