Please note: If this FAQ s empty you must choose English language from the drop-down-box below. Only English content is available as of now!
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
- Notification Services
- 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
- Instant Response
- Sitemap
Most popular FAQs 
- I get error 1130 "Host is not allowed to ... (115380 views)
- Error no. 2003: Can't connect... (52096 views)
- Error no. 1251: "Client does not support authentication..." (48093 views)
- Error no. 1045: "Connection denied..." (41340 views)
- SQLyog Version History (39954 views)
- What is HTTP-tunneling? (29291 views)
- Error No. 2005: Unknown MySQL server host... (28363 views)
- What Is SSH and SSH-tunneling? (25494 views)
- Why are Stored Procedures not created when I import ... (23460 views)
- Do I need PHP to use SQLyog with MySQL? ... (21519 views)
Latest FAQs 
- SQLyog Version History (2010-03-09 03:20)
- SQLyog is a client for the MySQL server - ... (2009-09-11 07:48)
- Can I use SQLyog with the various SQL-modes available ... (2009-08-20 08:02)
- Failed dependency for libstdc++.so.5 error (2009-08-13 11:22)
- Wrong results are returned for FOUND_ROWS(). (2009-08-12 06:31)
Working with Views, Stored Procedures and Triggers
Nested C-style comments fail with MySQL 5.1 and higher
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 5.1+ (but works before).
MySQL has confirmed this to be a server bug. At the time of writing this a patch is queued but not available yet.
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: We can only advice to 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 Webyog 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