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
17 Users online :: 17 Guests and 0 Registered
Most popular FAQs 
- I get error 1130 "Host is not allowed to ... (115181 views)
- Error no. 2003: Can't connect... (51972 views)
- Error no. 1251: "Client does not support authentication..." (48037 views)
- Error no. 1045: "Connection denied..." (41254 views)
- SQLyog Version History (39849 views)
- What is HTTP-tunneling? (29213 views)
- Error No. 2005: Unknown MySQL server host... (28251 views)
- What Is SSH and SSH-tunneling? (25437 views)
- Why are Stored Procedures not created when I import ... (23373 views)
- Do I need PHP to use SQLyog with MySQL? ... (21472 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)
SQLyog FAQ News
A Routine Upgrade Only
The upgrade of the FAQ system from version 2.0.2 to 2.0.4 is a routine upgrade only.
Users should not experience any difference.
However as 'promised' when we upgraded last time, we have 'cleaned up' in comments.
And this time more 'in depth' than last time!
Deleted were:
1) Comments and questions that should have been posted to our Forums instead.
2) Comments that are now irrelevant because it referred to functionalities that have been changed or issues that have been fixed (in SQLyog or in MySQL) in between.
Users should not experience any difference.
However as 'promised' when we upgraded last time, we have 'cleaned up' in comments.
And this time more 'in depth' than last time!
Deleted were:
1) Comments and questions that should have been posted to our Forums instead.
2) Comments that are now irrelevant because it referred to functionalities that have been changed or issues that have been fixed (in SQLyog or in MySQL) in between.
Last update: 2007-12-02 07:19
Author: Peter Laursen