|
DBSCHEMA for 2257 Database
I think its pretty complete...questions/suggestions are welcome
Performer Table
puid INTEGER Primary Key
Performer_Id BLOB (id type jgp png tif gif etc)
Performer_Fname VARCHAR (First Name)
Performer_Lname VARCHAR (Last Name)
Performer_Mname VARCHAR (Middle Name)
Peformer_DOB DATE (Birth date)
Performer_addy1 VARCHAR (address line 1)
Performer_addy2 VARCHAR (address line 2)
Performer_City VARCHAR (city)
Performer_State CHAR(2) (state)
Performer_zip VARCHAR (Zip code)
Performer_email VARCHAR (email addy)
Performer_phone VARCHAR (phone number)
Aliases Table
puid INTEGER
alias VARCHAR puid+alias = Primary Key
Shoots Table
Shootid INTEGER Primary Key
ShootDate DATE (Date of Shoot)
Location VARCHAR (Shoot Location)
Video CHAR(1) (Video Y/N)
Photos CHAR(1) (Photos Y/N)
ShootPerformers Table
shootid INTEGER
puid INTEGER shootid + puid = Primary Key
Website Table
Wid INTEGER Primary Key
WebsiteName VARCHAR (Site Name)
shootid INTEGER
url VARCHAR (URL of the photos or video in this shoot)
startfilename VARCHAR (the filename of the first file in the sequence of files that make up this shoot)
endfilename VARCHAR (The filename of the last file in the sequence)
Movies Table
Mid INTEGER Primary Key
Mname VARCHAR (movie name)
Shootid INTEGER
SceneNo SMALLINT (Scene number that this shoot appears in)
Notes: where attribute names are the same that attribute is a foreign key ie puid and shootid
mods can be added for canadian or overseas addresses if need be
shootdate can be checked against performerDOB to validate >= 18
Ok what am I missing and who will code the front end (PHP preffered)
__________________
Mike South
It's No wonder I took up drugs and alcohol, it's the only way I could dumb myself down enough to cope with the morons in this biz.
|