Databases
StackOverflow2013
Postsdbo
POSQL Structure of DB table with different types of columns
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL Structure of DB table with different types of columns
    primarykey
    data
    text
    <p>I have a problem with the optimization of the structure of the database. I'll try to explain it exactly.</p> <p>I create a project, where we can add different values​​, but this values must have different types of the columns in the database (eg, int, double , varchar). What is the best way to store the different types of values ​​in the database. In the project I'm using Propel 1.6. The point is availability to add value with 'int', 'varchar' and other columns types, to search the table was efficient.</p> <p>In total, I have two ideas. The first is to create a table of "value", which will have columns: "id ", "value_int", "value_double", "value_varchar", etc - with the corresponding column types. Depending on the type of values​​, records will be saved with the value in the appropriate column (the rest will be NULL).</p> <p>The second solution is to create separate tables such as "value_int", "value_varchar" etc. There would be columns: "id", "value", which correspond to the relevant types of "value" (ie, such as int, varchar, etc).</p> <p>I must admit that I do not believe any of the above solutions, originally I was thinking about one table "value", where the column would be a "text" type - but this solution would probably be even worse.</p> <p>I would like to know your opinion on this topic, maybe something else would be better. Thanks in advance.</p> <p><strong>EDIT:</strong> For example :</p> <p>We have three tables:</p> <p>USER: [table of users] * id * name</p> <p>FIELD: [table of profile fields - where the column 'type' is the type of field, eg int or varchar) * id * type * name</p> <p>VALUE : * id * User_id - ( FK user.id ) * Field_id - ( FK field.id ) * value</p> <p>So we have in each row an user in USER table, and the profile is stored in the VALUE table. Bit each profile field may have a different type (column 'type' in the FIELD table), and based on that I would want this value to add to the appropriate column of the appropriate type.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDmitry Dvornikov
    1. USDmitry Dvornikov
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSQL Structure of DB table with different types of columns
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSQL Structure of DB table with different types of columns
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODoing it the _normaized_ way isn't an option?
      singulars
      1. POSQL Structure of DB table with different types of columns
      1. USgeomagas
    2. CO@geomagas What do you mean with normalize? Database normalization?
      singulars
      1. POSQL Structure of DB table with different types of columns
      1. USDmitry Dvornikov
    3. COYep. Each value in a separate field with its type and all.
      singulars
      1. POSQL Structure of DB table with different types of columns
      1. USgeomagas
 

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