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 ... (128705 views)
- Error no. 2003: Can't connect... (58524 views)
- Error no. 1251: "Client does not support authentication..." (50542 views)
- Error no. 1045: "Connection denied..." (46251 views)
- SQLyog Version History (45078 views)
- Error No. 2005: Unknown MySQL server host... (33381 views)
- What is HTTP-tunneling? (32471 views)
- What Is SSH and SSH-tunneling? (28002 views)
- Why are Stored Procedures not created when I import ... (27057 views)
- Do I need PHP to use SQLyog with MySQL? ... (23936 views)
Latest FAQs 
- SQLyog Version History (2010-09-02 04:20)
- Do I need to replace the PHP tunneler file ... (2010-03-25 10:26)
- Data get truncated when importing a large CSV-file. (2010-03-18 12:30)
- 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)
Character Set and Localization Issues
Does SQLyog crash the MySQL server?
No generally not! But MySQL has confirmed a bug that causes the MySQL server to crash when the server has UCS2 as the default character set and a client attempts to connect. MySQL versions 4.1, 5.0 and 5.1 are affected.
It happens when connecting not only with SQLyog, but also PHP and MySQL's own GUI tools (MySQL Administrator, MySQL Query Browser). Probably any client (at least), that uses the C-API. MySQL command-line client is not affected. At this point of time it is not clear if the same thing happens with other connectors (ODBC, JDBC, Pearl, RUBY, Delphi wrapper class etc.)
It also is not yet clear if all mySQL 4.1, 5.0 and 5.1 versions are affected or if it is only the most recent builds. Read about the bug here: http://bugs.mysql.com/bug.php?id=18004
You can still use UCS2 charset as default for databases, tables and columns - but not as default for the server!
Write-up March 23rd 2006: MySQL has now committed a patch for this. It will be effective from MySQL versions 4.1.19, 5.0.20 and 5.1.8
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
- Installation and upgrading
- Buying and Licensing SQLyog
Last update: 2006-03-07 11:58
Author: Peter Laursen
Revision: 1.0
You can comment this FAQ