Let's say you have a simple member login table :
[color=dark-blue]id | username | password | email | user_type | last_log | IP | session | active | posts |[/color]
Then you have a member infos table
[color=dark-blue]id | first_name | last_name | address | city | country | zip | contact | website [/color]
Then you have a third table containing different field regarding the type of user
[color=dark-blue]id | company | jobs_posted | ppl_employed | user_rating[/color]
or
[color=dark-blue]id | jobs_found | employer_rating[/color]
Performance-wise, Is it better to keep these tables separated, or do you think it wouldn't lower performances to bind them ?
(for the third table set, all collumn would be there with null values for empty fields...)
[color=dark-blue]id | username | password | email | user_type | last_log | IP | session | active | posts |[/color]
Then you have a member infos table
[color=dark-blue]id | first_name | last_name | address | city | country | zip | contact | website [/color]
Then you have a third table containing different field regarding the type of user
[color=dark-blue]id | company | jobs_posted | ppl_employed | user_rating[/color]
or
[color=dark-blue]id | jobs_found | employer_rating[/color]
Performance-wise, Is it better to keep these tables separated, or do you think it wouldn't lower performances to bind them ?
(for the third table set, all collumn would be there with null values for empty fields...)
Comment