SQLyog MySQL GUI 12.4.2 Released

This maintenance release of SQLyog, MySQL GUI introduces a new feature – REGEX search in Object Browser – and adds a few bug fixes.

Changes as compared to MySQL GUI 12.4.1 include:

Important notice:

* The tunneler file for HTTP-tunnel has been updated with this release and must be replaced on the server.  Earlier HTTP-tunnel required PCRE-support in the server-side PHP-environment. Now it does not.


* Search function in Object Browser now supports regular expressions.

Bug Fixes:

* Fixed a rare connection failure using SSH-tunnel to specific BSD systems.
* Removed unnecessary virtual column check for older servers with no support for this.
* Fixed a crash when a menu-item, that is disabled in read-only mode , was clicked with no active connection tab.


* In Scheduled Backup wizard renamed the ’Flush Master Logs’ -option to ‘Purge Binary Logs’. This is in order to comply with ‘mysldump’. Further removed ‘Flush Slave Log’ -option, as using it on a replication environment could break replication.

Downloads: https://www.webyog.com/product/downloads
Purchase: https://www.webyog.com/shop


Add yours
  1. 1

    The RegExp functionality isn’t quite clear nor can I find instructions on how to use it.
    I’ve got a database named ‘Admin’. I tried the following regexps, but none matched the database:
    A, /A/, A*, /A*/, A.*, /A.*/, A%

    So…. how does it work?

  2. 3

    I am well versed in Regular expressions. But they are broken. I figured out what (some) of the problems are.

    A.* -> no results
    a.* -> ‘Admin’ as a result. (and more)
    A -> no results
    a -> results in ‘Admin’, ‘apache’, etc.

    It seems all database names are converted to lowercase before matching. Put any uppercase character in the regexp, and it fails.

  3. 4

    Hi Sander,

    We are using PCRE library for R.E. evaluation and matching. We are compiling it in a way to perform case insensitive matching (and we will be sticking to it) but for some reason that library is evaluating all the lower case expression correctly against lower case and upper case characters but not vice versa. We will be looking forward if we find any workaround for that. For now, you can simply type everything in lower case and expect it to give you upper case and lower case evaluation correctly.

    Best Regards,

      • 6

        Hi Sander,
        We suspect this is the bug with pcre. We may change the search string internally to lower case so that pcre matches it correctly, as you suggest. However, our PCRE version is quite old and upgrading the library may resolve this. We will check the best possible solution and update you accordingly.
        Best Regards,

+ Leave a Comment