Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: ocean10000
My question is that I and most of the developers that I have worked with have used dataType tables. For example, PageType, ProductType etc.
In a data model we are reviewing right now the developer is using a Types table that contains all dataTypes from all of the many tables of this database. This types table contains about 50 different dataTypes.
Now my question is what are some of your thoughts on this approach VS breaking the types into their own tables?
Thoughts and comments greatly appreciated.
If I can guess at what you are saying...there is no problem with breaking out related tables to be used specifically for their own purpose such as PageType, or ProductType which are related to the Page and Product tables.
If the PageType and ProductType tables are exactly the same schema though (same columns and data) then it could be feasible to keep them all in that table.
I've seen both and done both. If I had my druthers I'd set the types into their own tables. That takes some heat of one single type/config table.
Everyime I've either done or seen this it's because time was extremely limited so in my case I've always kluged it into a single table... but when I get the time then I prefer seperate tables.
As a simple starting point, 1 database table per entity isnt a bad approach.