mysql - Best structure for memorizing user details and preferences -


I have a domain where each user has some information such as height , weight < / Code>, eye color , hair color , ... about yourself, and your ideal partner ( favorite height Very similar data about) , preferred hair color , ... ).

I have to respect the user's characteristics and their preferences, keeping it in mind, what is the best structure in terms of functioning?

I mean, I can design like a table: Description (ID, height, weight, eyes, ...) and a user table: A table extension (ID, type, value) and an included table like user (id, ..., description_id, preferences_violence_id) or .

There are also other ways.

What do you choose and why? is a little late for a comment.

I decided to stop this question in particular because you are asking for an opinion and explanation. You should review the question on the stack overflow.

In addition to that, you have crushed in the area which can almost be a subject of religious zeal. Strong "relatives" want you to put all the columns in a column. And for good reason, supporters of the unit-attribute-value model (EAV) have been given strong arguments in favor of that approach and, they are hybrids between them. I suggest that you start by researching EAV models, you can understand what is more suitable for your particular environment.

Comments

Popular posts from this blog

Pass DB Connection parameters to a Kettle a.k.a PDI table Input step dynamically from Excel -

multithreading - PhantomJS-Node in a for Loop -

c++ - MATLAB .m file to .mex file using Matlab Compiler -