**GROUP**
id area
1 Multimedia
4 Education
**Employment**
id foreign key(GROUP) job
1 1 designer
2 4 professor
3 1 copy
and now suppose that i have this
**SpecificProperties**
id foreign key (Employment) properties
1 1 type of contract
2 1 number of jobs
3 2 duration contract (no type of contract)
4 2 number of jobs
the designer and the professor in this case have the property number of jobs. So basically the question is, i need repeat the number of jobs for each profession? there is any way to avoid? or i can have to number of jobs 8 foreign keys to 8 different jobs for example ? one for designer, other for professor, other for copy, and so on? in this way the first number of jobs have in the foreign key 1 || 2 || 3
something like this:
**SpecificProperties**
id foreign key (Employment) properties
1 1 type of contract
2 1||2||3||4 number of jobs
3 2 duration contract (no type of contract)
point of situation. i think that a many-to-many possible is not the best solution.
Please help me to reformulate the hierarchy of the database.
I have:
user (id, name, age, salary, profession)
professional area (id, area, number of members)
job (id, job)
statistics (average salaries, average age, and other stuff )
i am totally confused with that
What i pretend is just a simple interface like this:
So you are saying that the property “number of jobs” would have different data associated with it based on job? Is the “different data” for each property/job relation known (static) or will a user be able to add info for a property/job relation through an interface?