<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote/font><HR>Originally posted by KeithMcL: How's everyone today?
Ok, i'm trying to work out the best way to setup tables in my database for www.webmasterswork.com and I need your help on what tables I need to create etc.
My database is called webmasterswork_com and as far as I know i cannot rename it or create a second one.
Do I need to setup a table for the likes of category description, job title, date, salary, fulltime, partime, contract, consulting, etc?
Well, I'd set it up something like this.
Tables for users, jobs, companies, resumes, portfolios, portfolio items and resources.
user_id //primary key
address //if you want
job_id //primary key
user_id //posted by which user, ties to user table.
company_id //ties to company table
job_category //fulltime, parttime, contract, etc.
company_id //primary key
state //change the address fields to fit target, i.e. province, etc.
resume_id //primary key
user_id //who posted it, ties to user table
file_location //if you're going to have DOC files in a directory
body //if you're going to have ASCII or HTML resumes pasted in a form.
portfolio_id //primary key
user_id //ties to user table
This gives you most of what you need. The trickiest part is the portfolio bit. The item table just has a bunch of URL's and descriptions of them as well as an portfolio identifier. The portfolio table ties a user to a set of portfolio items.