- 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
- 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
55 users online | 55 Guests and 0 Registered
- I get error 1130 "Host is not allowed to ... (364916 views)
- Error no. 2003: Can't connect... (255561 views)
- SQLyog Version History (178627 views)
- Error no. 1045: "Connection denied..." (133792 views)
- Error No. 2005: Unknown MySQL server host... (105341 views)
- What is HTTP-tunneling? (91549 views)
- Can I use SQLyog with the WINE Windows emulator ... (87456 views)
- Error no. 1251: "Client does not support authentication..." (79084 views)
- What Is SSH and SSH-tunneling? (64424 views)
- The "DELIMITER" command does not have effect. Why is ... (57863 views)
- SQLyog Version History (2014-06-08 10:22)
- I get error 1130 "Host is not allowed to ... (2014-01-30 12:21)
- About CHUNKs and BULKs (2014-01-09 11:53)
- SQLyog is a client for the MySQL server - ... (2013-08-04 04:48)
- Problems creating a functional DSN on 64 bit Windows. ... (2013-07-22 08:34)
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.
- SQLyog Version History
- What encoding is used for files saved by SQLyog?
- Introduction to the 'SQLyog Job Agent' (SJA)
- I have problems with importing CSV data
- Can I add my own strings to SQLyog auto-complete?
You can comment this FAQ