I am working on a social networking site with a family tree that is GEDCOM-compliant. We need to decide that we should use horizontal or vertical database structure for user profiles. Therefore, I would like to know that when using a horizontal database structure, and when the vertical database structure is used, no one can answer.
I have received a few answers for shopping sites where the areas have not been decided: A vertical database structure should be used. But I am confused about what to use for family tree's site. Should I use vertical or horizontal?
I think you can post MySQL, Ms sql, Sqlite, Postgrescale or Oracle for storage?
Gedcom is a standard for information exchange so that you will know how many columns you have. Perhaps the standard is being extended with new qualities in the future but this will probably be used for many new qualities. You can easily expand the table with some new columns.
I will use a 'horizontal' table and not a unit-attribute-value-system (vertical table). Workbench table systems are slow. The query optimizer can not be properly indexed and confused.
It becomes a different story when your users can define new properties in their own profile such as eye colo (u) r or favorite colo (u). How do you want to make those profiles flexible?
No comments:
Post a Comment