Navigation
- FAQ Home
- All categories
- About Webyog support and about this FAQ
- About the SQLyog program

- Connection issues

- Using the GUI
- Managing your MySQL Database Systems

- Database Schema Synchronization
- MySQL DATA synchronization
- SQL Scheduler and Reporting Tool
- Importing external data
- Backup/Restore
- SQLyog Job Agent (SJA)

- Working with Views, Stored Procedures and Triggers
- Character Set and Localization Issues
- MySQL bugs that affect SQLyog
- Questions on Open Source and Compiling
- Sitemap
Most popular FAQs 
- I get error 1130 "Host is not allowed to ... (169314 views)
- Error no. 2003: Can't connect... (86270 views)
- SQLyog Version History (63952 views)
- Error no. 1045: "Connection denied..." (61346 views)
- Error no. 1251: "Client does not support authentication..." (58317 views)
- Error No. 2005: Unknown MySQL server host... (50192 views)
- What is HTTP-tunneling? (42282 views)
- What Is SSH and SSH-tunneling? (38071 views)
- Can I use SQLyog with the WINE Windows emulator ... (34944 views)
- Why are Stored Procedures not created when I import ... (34267 views)
Latest FAQs 
- SQLyog Version History (2012-01-26 08:20)
- SQLyog is a client for the MySQL server - ... (2011-11-04 04:48)
- I get error 1130 "Host is not allowed to ... (2011-11-01 05:21)
- Problems on Ubuntu 11.x (2011-10-29 13:02)
- Problems creating a functional DSN on 64 bit Windows. ... (2011-09-15 14:34)
Sticky FAQs
MySQL bugs that affect SQLyog
Nested C-style comments fail with MySQL 5.1
Nested comments written like /* external /* internal comment */ comment */ fail to execute with MySQL 5.1 and higher. It works before that.
That is a problem with 'stored programs' and Views. When dumping a Stored Procedure for instance SQLyog will (like 'mysqldump' and most other up-to-date programs) generate syntax like
DELIMITER $$
/*!50003 CREATE PROCEDURE ´sp1´()
BEGIN
/* a comment */
END */$$
DELIMITER ;
.. and you see the sequence /*! .. /* .. */ .. */ what fails to restore in some early 5.1 servers (but works with server versions before 5.1). Also some versions of (the discontinued) MySQL 6.0 have this problem. MySQL 5.5.x is not affected.
MySQL has confirmed this to be a server bug with specific 5.1 servers. The bug was fixed in MySQL 5.1.35 and onwards.
Related MySQl bug reports: http://bugs.mysql.com/bug.php?id=39559 and http://bugs.mysql.com/bug.php?id=44189 and http://bugs.mysql.com/bug.php?id=30631
As SQLyog will use the same comment construction internally in 'copy database' it also affects here.
Workaround: If you have an affected server version and for some reason do not want to or cannot upgrade the server you may use "-- comment" or "#comment" but not "/*comment*/" inside stored programs and Views.
Tags: -
Related entries:
- Do I need PHP to use SQLyog with MySQL?
- SQLyog gives you the most options for connecting to MySQL
- Welcome to the SQLyog FAQ
- SQLyog Version History
- What is and what is not imported by the SQLyog Import External Data Tool?
Last update: 2009-04-14 04:45
Author: Peter Laursen
Revision: 1.0
You can comment this FAQ