Question about Database

[eluser]slowgary[/eluser]
[quote author="mTuran" date="1245588248"]i can't join into one table. I want that because if all users both experts and employers is have unique id then managing will be more easy and confortable.[/quote]

This seems to contradict. Each 'expert' and 'employer' having a unique ID would be much easier and comfortable if they were in the same table. Also, they ARE the same... they're 'users'. I still think the better way would be to use 1 table for the users with unique IDs. Most likely, information would be duplicated otherwise. Won't every user have a password, email, and other similar fields? They belong in the same table. Instead of using a separate table for their unique IDs, use a separate table for attributes that don't belong to both 'experts' and 'employers' and tie them together with their ID. Also, you should not use the user's unique ID as the table's primary key. You should have an auto increment integer primary key, PLUS a unique ID index as the user's ID number. This will help you if you change your database structure in the future.