SitePoint Sponsor

User Tag List

Results 1 to 3 of 3
  1. #1
    Freelance Web Designer KeithMcL's Avatar
    Join Date
    Oct 1999
    Location
    Dublin, Ireland
    Posts
    1,125
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    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?

    Thanks

    ------------------
    Keith McLaughlin
    Soon to come,
    www.webmasterswork.com

  2. #2
    SitePoint Member
    Join Date
    Jun 2000
    Posts
    2
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    <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?

    Thanks

    <HR></BLOCKQUOTE>
    Well, I'd set it up something like this.

    Tables for users, jobs, companies, resumes, portfolios, portfolio items and resources.

    tbl_user
    user_id //primary key
    email
    password
    address //if you want


    tbl_jobs
    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.
    title
    description
    requirements
    contact_info
    posted_date
    expire_date

    tbl_company
    company_id //primary key
    company_name
    address
    city
    state //change the address fields to fit target, i.e. province, etc.
    postal_code
    company_industry
    company_URL

    tbl_resume
    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.
    posted_date
    expire_date

    tbl_portfolio
    portfolio_id //primary key
    user_id //ties to user table

    tbl_portfolio_items
    item_id //primary key
    portfolio_id //ties to portfolio table
    item_title
    item_description
    item_URL

    tbl_resources
    resource_id //primary key
    resource_title
    resource_description
    resource_URL


    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.

    If you need more explanation, let me know.

  3. #3
    Freelance Web Designer KeithMcL's Avatar
    Join Date
    Oct 1999
    Location
    Dublin, Ireland
    Posts
    1,125
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Wow jwynia, that really has helped. At least now I know where to start off from.

    Thanks a million.



    ------------------
    Keith McLaughlin
    Soon to come,
    www.webmasterswork.com


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •