Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Have you considered breaking up your permissions table into a set of tables that each apply to a separate table of objects, for instance tier_1_assets and tier_1_permissions, and tier_2_assets and tier_2_permissions. This will make it simpler to query the permissions for a tier of assets, but more complex to query for all the permissions of a user (this is a trade off).</p> <p>I would also challenge the assumption that a relational database is the right storage medium for your data. It may indeed be, but may also not be. (PHP may limit freedom in that respect).</p> <p>If your data set is small, why not save it to a single serialized file, and have a small server that keeps it in memory and provides a query interface? I am sure there are good reasons why not. (In addition to being in PHP)</p> <p>Have you considered multiple point tables for your second problem? It may feel like a repetition, but it does make life simpler for some kinds of look ups, and is normalized when you consider each foreign key reference as a different type of object (you get to use foreign key checks on them when the tables are separated).</p> <p>The multiplicity of the relationships between objects should tell you where to put your keys and references: one-to-many -> (key &lt;- foreign key); many-to-many -> (key &lt;- link-table -> key); one-to-optional -> (key &lt;- foreign key).</p> <p>I do not know of any patterns that match your problem as it was stated. But I have noticed that most generic solutions to avoid creating another table get really hard to manage very quickly.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs there a normalized form for representing several objects from different tables?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSarah Happy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs there a normalized form for representing several objects from different tables?
      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. COCan you think of a significant advantage to one point table per device versus point info stored in each device's table on nullable columns?
      singulars
      1. PO
      1. USDereleased
    2. COYou could also consider three tables, device, point, and device_point, that would let you search by points and by device, and not have your nullable columns. I view nullable columns as a sign that a table maybe should be broken up.
      singulars
      1. PO
      1. USSarah Happy
    3. COI have accepted your answer as we decided to challenge the assumption that a relational database was the correct storage medium for this project and have instead relegated the actual device data storage to a separate mechanism elsewhere in the project; this way, the points table need only be aware of the module that data is stored in, and the ID it is stored as in said module, and other than that can simply store the appropriate map-related data. Thus, the points table is now the only table needed. Sometimes, I guess I just need to put down the MySQL "Hammer".
      singulars
      1. PO
      1. USDereleased
 

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