Databases
StackOverflow2013
Postsdbo
POObject and Object meta schema design
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POObject and Object meta schema design
    primarykey
    data
    text
    <p>Am working on a project that will save many types of objects into the database. These include: articles, polls, writers .. etc. Some of those are unknown to me at design time so what i am trying to do is build a generic table schema that will enable me to save any type of item into this database.</p> <p>My design</p> <p><strong>Table Object</strong></p> <pre><code>objectID int title varchar body text type int #will represent the ID of the type of object am inserting </code></pre> <p>Having that circumstances or requirements might need additional data, i decided that this will go to what i call "object metadata" as follows:</p> <p><strong>Table Object_MetaData</strong></p> <pre><code>metaID int metaKey varchar metaIntKey int #representing an integer value of metaKey which is calculated using some algorithm to speed up queries metaValue varchar(1000) </code></pre> <p>I am doing all the work in PHP and MySQL btw.</p> <p>A couple of things came up to my mind when doing this design regarding the performance of the database on the long run:</p> <p>1) Is saving int, boolean, small text, big text into the metaValue effecient?</p> <p>2) on the long run the metadata table is going to grow quite quickly. Is this a maintainance nightmare? how is MySQL going to to handle this?</p> <p>3) IN php when fetching objects, i will have to loop each object to fetch its metadata, or load all metadata once using lazy loading or load any single metakey once its requested via __get magic method. So when fetching a list of say 50 objects, at least 50 select statements will be executed when using any of the methods i suggested. Is there a better more efficient way of doing this?</p> <p>Any thoughts or comments on this design are welcome.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMaverick
    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. POObject and Object meta schema design
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POObject and Object meta schema design
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POObject and Object meta schema design
      1. USMaverick
      1. VTFavorite
    1. This table or related slice is empty.
 

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