Hello,
we currently have a small database setup for affilates and visitor/leads. I
believe we have a "one to many" application, one affiliate can have several
visitor/leads but each visitor can only be assigned to one affiliate.
What I need to know if this the best design for this setup. Basically a visitor
fills out a form, and is assigned to one affiliate. So I was wondering is it
better to create a " joining table" between the `affiliates` table and the
`visitors` table or will this design be efficent as it is. Below are the 2
tables in question
CREATE TABLE IF NOT EXISTS affiliates (
affid int(6) unsigned NOT NULL auto_increment,
affiliate_id int(10) unsigned NOT NULL default '',
affiliate_email varchar(60) NOT NULL default '',
PRIMARY KEY (affid),
KEY affiliate_id (affiliate_id)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
CREATE TABLE IF NOT EXISTS visitors (
visitorid int(6) unsigned NOT NULL auto_increment,
fname varchar(20) NOT NULL default '',
lname varchar(20) NOT NULL default '',
phone varchar(20) NOT NULL default '',
email varchar(60) NOT NULL default '',
state char(2) NOT NULL default '',
ip varchar(20) NOT NULL default '',
dtime datetime NOT NULL default '0000-00-00 00:00:00',
exported varchar(10) default NULL,
affid int(6) unsigned NOT NULL default '0',
PRIMARY KEY (visitorid),
KEY email (email),
KEY affid (affid)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
TIA,
--
Mike(mickalo)Blezien
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Thunder Rain Internet Publishing
Providing Internet Solutions that work!
http://thunder-rain.com/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
