Bug #14470 /* .. */ multi-line comment sytax not working
Submitted: 29 Oct 2005 17:28 Modified: 4 Jan 2006 15:14
Reporter: Mike Fried Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Query Browser Severity:S2 (Serious)
Version:1.1.17 OS:Windows (Windows 2003)
Assigned to: Mike Lischke CPU Architecture:Any

[29 Oct 2005 17:28] Mike Fried
Description:
The /*...*/ multi-line syntax is not working correctly in the script editor.  You get error messages for every line of code between the Comment Start (/*) and End (*/) lines.  This was working fine in Version 1.1.15, but is now failing in 1.1.17.

The Inline /*..*/ Comment syntax is working correctly.  Just a problem with the multi-line syntax.  Something changed between versions 1.1.15 and 1.1.17 to break this functionality.

The Uncommented portions of the script run correctly, but the commented out portions should be ignored.  They are grayed out on the display but are still executed by the engine.

How to repeat:
Running the following script will generate the Error:

/*
Purpose		To Create the Initial Application Server Database Structure
Steps		1.  Create Base Tables
			TBL_TABLE_1
			TBL_TABLE_2
			TBL_TABLE_3
		2.  Add Initial "Seed" Data to Tables
			TBL_TABLE_1
			TBL_TABLE_2
			TBL_TABLE_3
		
Modification History:
---------------------
Created	By:		Author
Date Created:		10/29/2005

Modified By:		
Date Modified:		
Notes:			

*/

/******** CREATE ALL Base Tables *************/

-- ------------------------------------------------------------

-- CREATE TABLE `TBL_TABLE_1`

CREATE TABLE `TBL_TABLE_1` (
	`Column1` INT NOT NULL AUTO_INCREMENT ,
	`Column2` VARCHAR(100) NOT NULL ,
	`Column3` VARCHAR(1000) NOT NULL DEFAULT '' ,
	`Column4` BIT NOT NULL DEFAULT TRUE ,
	CONSTRAINT `PK_TBL_TABLE_1` PRIMARY KEY 
	(
		`Column1`
	) 
) ENGINE = INNODB, AUTO_INCREMENT = 101;

-- ---------------------------------------------------------------------

-- Rest of Script removed for brevity
[4 Jan 2006 15:14] Mike Lischke
I cannot reproduce this problem with the actual sources. Since a lot of work
went into the Script Editor since October I assume this particular problem also
has been fixed in this process. Please verify that with the current or next
release of QB and reopen this bug report if you still see the mentioned
problem.

Mike