not parsing comments properly?

[Shadow]

Interesting, SQLyog does not seem to regard line breaks as termination of comments. Should be corrected…

[number_one]

I mentioned this way back with the release of SQLyog 3.5

Comments with the pound sign will no longer work because it wraps everything onto one line before parsing it as of version 3.5. Before that, it parsed each line with carriage return separately. So now the only way to reliably use comments is by enclosing a comment with /* */ type indicators.

Very, VERY annoying for someone who uses comments frequently and would like to comment out a very long query by simply putting a pound sign in front. I don't know why it hasn't been corrected, and IMHO there is no valid reason to say that this change is “by design”.

PLEASE, PLEASE fix this so I can stop using version 3.11

[Ritesh]

This bug was fixed in SQLyog 3.62. I executed the following sql in SQLyog 3.62 & 3.63 –

Code:

#this is a comment
alter table `ritesh`.`db` ,change `Db` `Db` int (64)   NOT NULL ,drop primary key, add primary key (`Host`, `Db`, `User` );

The outputs are given in the attached images. I executed the above statement using F5 and Shift+F5.

SQLyog strips off all the carriage return characters before adding them to the History window. It will send the query to MySQL as entered by the user.

[Ritesh]

The above bug was present in SQLyog 3.61 as reported by nelson1993

[Author]

Posts