hi...
i created the following simple test of sql for mysql. i included some
comments that use the word 'system' in the comments. the comments are
wrapped in the '/* ... */' delimiters..
i get an error stating 'sh: foo command not found.' i traced the error/msg
to the fact that the word 'system' is in the comments. when i remove it, the
error/msg goes away...
any thoughts/comments/etc...
thanks
bruce
[EMAIL PROTECTED]
-- MySQL dump 10.9
--
-- Host: localhost Database: spyder
-- ------------------------------------------------------
-- Server version 4.1.12-standard
/*
mysqldump --no-data --tables -uroot -p dbname >colleges_schema.sql
mysql -uroot -p dbname < colleges_schema.sql
*/
-- setup spyder database
use spyder;
/*
initial schema for the 'spyder' app...
the following tables are initially used....
tables-
TermTBL - Lists the Terms for the app
(Fall/Spring/Etc...)
YearTBL - Lists the Years for the app
(2006,2007,2008...)
SemesterTBL - Lists the Semesters/Years for the app
ServerTBL - Lists the Servers used for the network
ProcessTypeTBL - Lists the Process types (Dev/Test/Prod)
BatchFileTBL - Batch File Information
BatchFileStatusTBL - Batch File Status
BatchFileHistTBL - Batch File History
ParsingScriptTBL - Script Information (colleges/names)
ParsingScriptCurrentTBL - Scripts (updated list of script
information -latest information,
process/semester)
ParsingScriptHistoryTBL - Script History (complete/historical
information regarding the scripts.
all updates/changes (process/semester)
as the script moves in the system
is maintained here..)
ParsingScriptHistoryStatusTBL - Script Status (complete status
for the script file is maintained
in the tbl. this table combines
information from
ParsingScriptHistoryTBL with the
various status generated running
the given script. each script will
produce multiple status during the
run.)
BatchFileParsingScriptTBL - Links Batch Files to Parsing Script
UniversityTBL - University List/Information (complete
information regarding the given
college)
UserTBL - User Information (maintains complete
information regarding the various
users for the system. includes
developers/testers/admins/etc...)
ServerStatusTBL - Server Status Information
ServerHistoryTBL - Server History/Information
SvnTBL - Subversion Repository Information
DeptTbl - Department listings information
spyderInstructorTBL - Instructor information
InstructorTBL - master Instructor information
CollegeSemesterTBL - Links Colleges/Semester information
StateTBL - States
*/
--
-- Table structure for table `SemesterTBL`
--
/*
provides the Semester/Year data
Semester - (Fall/Spring/Summer/Summer I/Summer II)
Year - The year
the idea is to allow the user to populate the TermTBL
with the various terms
Terms - (Fall/Spring/Summer/Summer I/Summer II/Etc...)
the user would also populate the YearTBL with the years
Year - (2005/2006/2007/etc...)
The SemesterTbl could/would then contain a list of the
semester/year combinations, which would then be displayed
in the Semester Drop Down List...
Although there might not be a need for the SemesterTBL, if
the spyder app dynamically generated the Semester from the
Term/Year Tbls...
*/
DROP TABLE IF EXISTS TermTBL;
CREATE TABLE TermTBL (
Term varchar(50) NOT NULL default '',
ID int(5) NOT NULL auto_increment,
PRIMARY KEY (ID),
UNIQUE KEY term (Term)
) TYPE=MyISAM DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS YearTBL;
CREATE TABLE YearTBL (
Year int(4) NOT NULL default '',
ID int(5) NOT NULL auto_increment,
PRIMARY KEY (ID),
UNIQUE KEY year (Year)
) TYPE=MyISAM DEFAULT CHARSET=latin1;
DROP TABLE IF EXISTS SemesterTBL;
CREATE TABLE SemesterTBL (
SemesterYear varchar(50) NOT NULL default '',
ID int(5) NOT NULL auto_increment,
PRIMARY KEY (ID),
UNIQUE KEY semester (SemesterYear)
) TYPE=MyISAM DEFAULT CHARSET=latin1;
--
-- Table structure for table `CollegeSemesterTBL`
--
/*
system of the semester information. This gets updated for each
*/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
