enrique...

i wasn't looking for away around the behavior... i was simply posting this
as a potential bug.

my version of mySQL (1.4.12) gives me the error that i described.. i'd be
willing to bet other versions act in a similar manner...

-bruce


-----Original Message-----
From: Enrique Sanchez Vela [mailto:[EMAIL PROTECTED]
Sent: Monday, August 01, 2005 7:21 PM
To: [EMAIL PROTECTED]; mysql@lists.mysql.com
Subject: RE: possible mysql/sql error...



Bruce,

the shell is catching "system" and tries to execute
whatever follows it,  MySQL ignores it 100%.

try using 'system' intead of the bare word and see.

regards,
esv.


--- bruce <[EMAIL PROTECTED]> wrote:

> to recreate the error...
>
> make sure you have a test database/etc setup...
> create the following test sql file
>
> --------------------------------
> sample.sql
> --
> -- test comments
> --
> /*
>   system of the semester information. This gets
> updated for each
> */
>
>
> import/run the sample.sql
>
> mysql -ufoo -p dbname < sample.sql
>
> you'll get the error....
>
> the error is generated because the mysql parser
> seems to see the 'system'
> word in the comment field and it interprets it as
> being the 'system'
> function that can be run from within mysql, that's
> used to run external
> system functions... however, given that the word
> 'system' is inside a
> comment, it should be ignored!!!!!!!
>
> if you place aomething in front of the 'system' in
> the comment.. it gets
> ignored...!!!
>
> hope this clarifies what i  stated earlier...
>
> -bruce
>
>
>
> -----Original Message-----
> From: bruce [mailto:[EMAIL PROTECTED]
> Sent: Sunday, July 31, 2005 1:15 PM
> To: mysql@lists.mysql.com
> Subject: possible mysql/sql error...
>
>
> update...
>
> it appears that the 'system' word has to be at the
> beginning of a line in
> the comment for the error to occur!!!!!
>
> i'm willing to bet this is a bug that hasn't been
> filed!!!! what are the
> odds that someone would run across it!!
>
>
>
> 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]
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
>
http://lists.mysql.com/[EMAIL PROTECTED]
>
>


Enrique Sanchez Vela
email: [EMAIL PROTECTED]
----------------------------------------------------------------------------
-
It's often easier to fight for one's        ||    We live in the outer space
principles than to live up to them        ||    Rev. Kay Greenleaf
Adlai Stevenson                                ||



____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to