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
8 users online | 8 Guests and 0 Registered
Most popular FAQs 
- I get error 1130 "Host is not allowed to ... (169226 views)
- Error no. 2003: Can't connect... (86215 views)
- SQLyog Version History (63913 views)
- Error no. 1045: "Connection denied..." (61323 views)
- Error no. 1251: "Client does not support authentication..." (58309 views)
- Error No. 2005: Unknown MySQL server host... (50162 views)
- What is HTTP-tunneling? (42269 views)
- What Is SSH and SSH-tunneling? (38047 views)
- Can I use SQLyog with the WINE Windows emulator ... (34918 views)
- Why are Stored Procedures not created when I import ... (34261 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
ID #1140
Special characters entered from 'mysql' command line display wrong in SQLyog (and vice versa).
This is not a bug with SQLyog and MySQL AB does not consider it a bug with the command line either. It is a 'limitation' with the Windows 'cmd.exe' program. The Windows 'mysql.exe' command line client is implemented in Windows 'cmd.exe'.
You can be perfectly sure that what SQLyog does is correct and what MySQL command line does is wrong!
Refer to: http://bugs.mysql.com/bug.php?id=31162
Also there is a limitation with the command line 'source' statement. It does not support unicode (neither utf8 nor utf16). However 'source' statement does support special ANSI characters (like accented European characters).
Refer to: http://bugs.mysql.com/bug.php?id=29323
One effect of this bug is that it is not possible to source a utf8-encoded DUMP from command line client on Windows when also the file itself is utf8-encoded.
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
- Installation and upgrading
- Buying and Licensing SQLyog
Last update: 2007-09-25 07:34
Author: Peter Laursen
Revision: 1.0
{translationForm}
You can comment this FAQ