Recruitment - the art of matching qualified applications to openpositions within an organization - is one of the most challenging tasks forany Human Resources department. However, powerful open-source tools likePHP and mySQL have made the process simpler, more efficient and moreeconomical than at any time in the past. This case study demonstrates how,by building a complete job listing and resume management system fromscratch.
Finally, I have some ancillary tables which store country lists, industry lists, subject lists and the like. Again, these have been placed in separate tables and linked via foreign keys to simplify customizing the application for diverse needs. Here they are:
#
# Table structure for table 'country'
#
DROP TABLE IF EXISTS country;
CREATE TABLE country (
id tinyint(4) unsigned NOT NULL auto_increment,
country varchar(255) NOT NULL,
PRIMARY KEY (id)
);
#
# id - unique record identifier
# country - country name
#
#
# Dumping data for table 'country'
#
INSERT INTO country (id, country) VALUES ( '', 'Afghanistan');
INSERT INTO country (id, country) VALUES ( '', 'Albania');
#
# Table structure for table 'degree'
#
DROP TABLE IF EXISTS degree;
CREATE TABLE degree (
id tinyint(3) unsigned NOT NULL auto_increment,
degree varchar(255) NOT NULL,
PRIMARY KEY (id)
);
#
# id - unique record identifier
# degree - degree type
#
#
# Dumping data for table 'degree'
#
INSERT INTO degree (id, degree) VALUES ( '1', 'High School degree');
INSERT INTO degree (id, degree) VALUES ( '2', 'Undergraduate degree');
INSERT INTO degree (id, degree) VALUES ( '3', 'Bachelor\'s degree');
#
# Table structure for table 'industry'
#
DROP TABLE IF EXISTS industry;
CREATE TABLE industry (
id tinyint(4) unsigned NOT NULL auto_increment,
industry varchar(255) NOT NULL,
PRIMARY KEY (id)
);
#
# id - unique record identifier
# industry - industry type
#
#
# Dumping data for table 'industry'
#
INSERT INTO industry (id, industry) VALUES ( '1', 'Advertising');
INSERT INTO industry (id, industry) VALUES ( '2', 'Agriculture and
Forestry');
#
# Table structure for table 'subject'
#
DROP TABLE IF EXISTS subject;
CREATE TABLE subject (
id tinyint(3) unsigned NOT NULL auto_increment,
subject varchar(255) NOT NULL,
PRIMARY KEY (id)
);
#
# id - unique record identifier
# subject - subject name
#
#
# Dumping data for table 'subject'
#
INSERT INTO subject (id, subject) VALUES ( '', 'Accounting');
INSERT INTO subject (id, subject) VALUES ( '', 'Actuarial Science');
The "jobs.sql" file in the source code archive contains a longer list of
items for these ancillary tables.
How many tables is that? Well, Joe, it's lucky number thirteen! Whoopee!
This article copyright Melonfire 2001. All rights reserved.
/ 4 
