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.
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: