Databases
StackOverflow2013
Postsdbo
POHow to design these two tables?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to design these two tables?
    primarykey
    data
    text
    <p>I want to build an application that allows a user to build its own form(s).<br> A user can input data into its form and query the data too. The form can be edited after being created and used ( add/remove fields from it ). The form can have small text box, big text box, single list, check box, or a drop down menu.</p> <p>I've been reading and asking around about which approach is better for building this kind of databases and I got no straight/good answer. I read that in this kind of application, the column based design (and representing each field as a column) is not a good idea since a user can be adding many fields and this is not a good idea, since there should be a limit on the number of columns in a table. However, I can't know in advance how many fields the user will add. (I'm not sure what they mean. It will help a lot if you explain further by giving an example.)</p> <p>I thought a good idea might be to group the fields according to their types. (type 1: text box , type 2: drop down list, type 3 : single list... and so on). I want to design my tables so that I can upgrade my application and add a new type any time I want without ALTERING my schema. So I was thinking to have 2 tables, one table to hold the metadata about the field: its type, its name, its position maybe in the form and another table to hold the actual value of the field. I can't seem to know what exactly to have in these tables and how to design them correctly. Your help is highly appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBill the Lizard
    1. USPeacefulSoul
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to design these two tables?
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. POHow to design these two tables?
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. POHow to design these two tables?
      1. This table or related slice is empty.
      1. VTClose
    1. COPeaceful, what is the intention for the app? If I understand correctly, you want any user to be able to create their own form, that presumably others can then use to fill in information? Would it be accurate to think of this as a kind of 'SurveyMonkey' where people can create surveys for others?
      singulars
      1. POHow to design these two tables?
      1. USsscirrus
    2. COThe last part of your question is the answer to your question. One table describes the fields of the form, and another holds the response values. Those different pieces of metadata (type, name, position) are columns of the metadata table.
      singulars
      1. POHow to design these two tables?
      1. USDan Grossman
    3. COyes i know ! but i dont know what exactly to put in these two tables so that if i want to add another type later on..i wont have to alter the schema.. say at first i had only text boxes and single list..then after ..i decided to let users use a dropdown menu...how should these two tables be in order to give me flexibility in adding new types without changing the schema..better said, are these 2 tables enough ??
      singulars
      1. POHow to design these two tables?
      1. USPeacefulSoul
 

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