Database planning...

Valkrin

I have a table of employees, the employees can work in many different location. So I have a one to many relationship (I think). Now should I have table like so:

Employees Table

employee_id | location_id | etc | etc

Or should I create another table like so:

Blah Table

location_id | employee_id

In the Blah Table one location could have many employees. So what should I do? Blah Table or keep the Employees Table that I already have.

Oh, and I also have a location table:

Location Table

location_id | address | state | etc | etc

Any help would be appreciated, thank you.

cahva

Well, I think you should keep all the tables! I think that is very smart thing to do with the blah-table. With that you could easily get the information who is working where, how many people work in some location etc.

You dont need location_id in your employee table. If employee can work in many places, you just add it to blah-table.

When you have added a couple of emplyees and their locations the blah-table should be looking something like this:

employee_id | location_id
-------------------------
|     1     |     1     |
|     1     |     2     |
|     2     |     1     |

... And so on.

What else to say... Thats basic normalization me thinks.

Valkrin

Thanks, I just needed to make sure I was on the right track. I think I am finally getting this database normalization down, in the beginning it would make my head spin. 🙂