Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I highly recommend you check out <a href="http://www.couchdb.org" rel="nofollow noreferrer">CouchDB</a> for this.</p> <ol> <li>You communicate with CouchDB using a straightforward REST API. In other words, it is "<strong>Made</strong> of the Web" rather than simply being a backend db like MongoDB and others. CouchDB can actually serve the forms and receive submissions since has a built-in web server.</li> <li>Being a JSON document store it is well-suited for storing structured-yet-schemaless data. (Forms and their submissions are really documents and it makes more sense to model them this way, IMO.)</li> <li>You could easily store a JSON document that describes each web form in the same "bucket" as the form submissions. (CouchDB can even parse form POSTs and turn them into JSON docs however you see fit. Having it automatically timestamp form submissions, for example, is simple.)</li> <li>You could write what is known as a "_show" function to actually generate each form's html code within CouchDB. Also check out "_update" and validation functions.</li> <li>It has the security features you would need.</li> <li>Document conflicts can be identified easily. Even better, CouchDB automatically determines a "winning" version of the document but you will continue to have access to the "losing" document versions (until you tell CouchDB to compact the database, which removes old revisions.) <ul> <li>Regarding uniqueness: instead of having CouchDB generate unique doc _id's you'll want to assign an _id that truly represents a unique form submission. If each user is only allowed one submission per form then use something along these lines for each JSON document created from a form submission: <code>submission:user:5:form:a3df2a712</code></li> </ul></li> </ol> <p>Using CouchDB you can avoid the pain of dynamically creating unique tables for every form a user might create.</p>
    singulars
    1. This table or related slice is empty.
    1. POUser-created database structure: non-relational or relational databases?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBen Damman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUser-created database structure: non-relational or relational databases?
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have looked into both MongoDB and CouchDB. They seem to be a good solution for this type of dynamical structure. Have you tried the former one also?
      singulars
      1. PO
      1. USnever_had_a_name
    2. COMongoDB is very different. For what you want to do--which involves serving and processing web form responses--couchdb seems a much better fit. MongoDB does not have a built-in web server and isn't able to internally handle forms. Of course, you can always use MongoDB for just storing JSON data. But CouchDB gives you a number of tools built-in that you otherwise have to write yourself.
      singulars
      1. PO
      1. USBen Damman
    3. COYou may want to check out how CouchApps work. (http://www.couchapps.org) CouchApps are a perfect example of something MongoDB can't provide because it's "just" a database.
      singulars
      1. PO
      1. USBen Damman
 

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