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 ... (169224 views)
- Error no. 2003: Can't connect... (86215 views)
- SQLyog Version History (63912 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
About Webyog support and about this FAQ
SQLyog is a client for the MySQL server - but what server versions are supported?
The points below summarizes the situation as of November 2011:
1) We support any MySQL version (whether official MySQL builds or 'fork' builds) that a recent standard MySQL client library can communicate with. That is from 3.23 to 6.x.
2) However any report of issues with a 3.23 version that is not 3.23.58 and any 4.0 version that is not 4.0.26 or 4.0.27 will trigger the standard reply "We don't care" if the issue can be resolved by upgrading to 3.23.58 or 4.0.26+.
3) for 4.1, 5.0, 5.1 and 5.5 versions we also "do not care" about issues with alpha/beta/RC versions if issue can be resolved by upgrading to a stable/GA version in the same tree.
4) for 4.1 specifically we recommend 4.1.20 or higher. Some Linux distributions (most important RHEL4) originally shipped with 4.1.10. This version has serious bugs in charset handling (of which most were fixed in 4.1.12). Official RHEL 4.1.20 builds are available for upgrade by RHEL4 users.
5) for 5.0 specifically we recommend 5.0.67 or higher.
6) for 5.1 specifically we recommend 5.1.35 or higher.
7) for 5.5 specifically we recommend 5.5.16 or higher.
8) for all stable/GA releases it also may happen that we will not resolve an issue if an upgrade to latest stable versions resolves the issue. It depends on the nature and seriousness of the issue and the effort required to fix or 'work around' the issue with the older version.
9) for versions that are only available as alphas/betas/RCs (currently anything higher than 5.5) we will consider only the most recent version released at the time of reporting. There is no guarantee that we will resolve an issue with those if we do not consider the issue critical. We may decide to 'wait and see' as there are often significant change of functionality with each new release of those early builds.
10) and finally versions only available from special branches and servers built from with latest committed source from the source code development trees we will generally not take action if no other build is affected and if it is not obvious that there is a bug that should be fixed under any circumstance.
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: 2011-11-04 04:48
Author: Peter Laursen
Revision: 1.0
You can comment this FAQ