# 4/2000 In Database "preferences"

#  table structure for site_preferences
CREATE TABLE site_preferences ( 
	id mediumint(200) DEFAULT '0' NOT NULL auto_increment, 
	username varchar(20), 
        password varchar(20), 
        serialno varchar(30), 
        site_title varchar(50), 
        bgcolor varchar(10), 
        textcolor varchar(10), 
        linkcolor varchar(10), 
        vlinkcolor varchar(10), 
        fontsize varchar(1), 
        hfont varchar(50), 
        linkhead1 varchar(20), 
        links1 blob, 
        linkhead2 varchar(20), 
        links2 blob, 
        linkhead3 varchar(20), 
        links3 blob,
        chaton varchar(3), 
        status varchar(12), 
# could use a TIMESTAMP for these dates, but I want the months,days,years to be easily parsible
        created_month varchar(2), 
        created_day varchar(2), 
        created_year varchar(4), 
        last_accessed_month varchar(2), 
        last_accessed_day varchar(2), 
        last_accessed_year varchar(2),
        last_modified_month varchar(2), 
        last_modified_day varchar(2),
        last_modified_year varchar(4),
        password_hint varchar(100),
        PRIMARY KEY(id), 
        UNIQUE id (id)

); 

CREATE TABLE ActiveUsers   ( 
    serialno varchar(30) NOT NULL, 
    ip varchar(120),  # to allow for sometimes long dynamic IP addresses
    # userprefs blob,  will be a CachedRowSet stored to the DB
    PRIMARY KEY (serialno), 
    UNIQUE id (serialno)
			   ); 

# table structure for allowed_links
CREATE TABLE allowed_links  ( 
    id mediumint(200) DEFAULT '0' NOT NULL auto_increment, 
    title varchar(50), 
    url varchar(255), 
    PRIMARY KEY(id), 
    UNIQUE id (id)
); 

# table stucture for user_info
CREATE TABLE user_info  	 ( 
  id mediumint(200) DEFAULT '0' NOT NULL auto_increment, 
  serialno varchar(20), 
  browser varchar(150), 
  java_enabled varchar(6), 
# a list of plugins can be long, so 255 characters may be too short, using blob instead
  plugins blob,  			
  PRIMARY KEY(id), 
  UNIQUE id (id)
);