Version History - 2017
SQLyog 12.4.3 (June 2017)
--This maintenance release upgrades the MariaDB Connector/C to version 2.3.3 (current). Versions before this could time out incorrectly on some environments (and for unclear reasons). Affected in particular was Windows 8, but also all Windows versions running in a virtualized environment could be.
SQLyog 12.4.2 (May 2017)
- 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.
SQLyog 12.4.1 (March 2017)
--Added an option to HEX-dump binary data in Export as SQL and in Scheduled Backup.
--In read-only mode FLUSH-statements can now be executed from the GUI as well as editor, except for ‘FLUSH TABLE WITH READ LOCK’ (as we don’t allow acquiring explicit LOCKS in read-only mode).
- Bug Fixes:
--On enabling HTTP, SSL or SSH checkbox in the connection manager, the checkbox wasn’t re-drawn automatically. The checkbox were re-drawn only on hovering over them or switching to another tab in the connection window
--In Table Diagnostics, clicking on Analyse executed same query irrespective of ‘Local’ being checked or not.
--Changed the row count in Data Synchronisation Wizard to use a 64-bit integer. Before this the rowcount displayed would stop incrementing at a 10-digit number.
--Import from Excel did not handle cells with multiline text properly. A linebreak became a SPACE.
--For a non read-only connection, on right-clicking on a table, the Import External Data option was greyed out even though it could be accessed from the Powertools and shortcut key.
--The ‘date picker’ did not handle dates with a ZERO-day/month/year (as allowed in specific sql_modes). In such cases current date would be selected and inadvertedly clicking “OK” in the dialog would overwrite. Now nothing is selected and the OK button is ‘greyed out’ in such cases.
--Fixed a rare crash occurring when editing the password for a connection.
--Regression fix: In SQL backups an extra \r was added for every \r\n in stored routines.
--Schema Sync sometimes failed to sync indentations to target exactly like on source.
SQLyog 12.4.0 (January 2017)
--Added an option for defining a connection as ‘read-only’. There is a checkbox in the connection settings and when checked the title bar will inform user about the ‘read-only’ state. In ‘read-only’ state statements that write cannot be executed. For more details please see note at the bottom.
--Added support for the MariaDB auth_gssapi (Kerberos) plugin. This plugin is available with the latest 3.0 (alpha) Connector/C from MariaDB. But there seems to be a huge popular demand for this already, and we have backported it to the 2.3 connector version we use in SQLyog. Note that support for this plugin is not available with SJA for Linux with this release.
- Bug Fixes:
--In User Manager, if a MySQL username contained certain special characters (including “@”), it was not possible to GRANT privileges TO or DROP the user due to misplaced quotes in the generated SQL.
--Adding a new user in the ‘User Manager’ wasn’t populating the the newly added user_name in the ‘User’ field.
--On localized keyboards with an ALTGR key, this key unintentionally behaved like CTRL with autocomplete popups. With some such keyboards using a non-QWERTY layout, this could prevent typing of specific characters.
A note about ‘read-only’ connections:
With the read-only flag checked in the settings for a connection, ‘read-only’ is enforced client-side from the SQLyog GUI and the editor no matter if user’s server-side privileges allows for writes. In ‘read-only mode’ you will be able to retrieve data from the server, use user variables, define SESSION-scope of server variables and everything else you need to work with data as long as you don’t need to write to the server.
In the GUI, controls that trigger statements that write to the database are ‘greyed out’ and do nothing. In the editor the same statements will be caught and not sent. This is accomplished by filtering against a ‘positive list’ of statements that are allowed. They are SHOW, SELECT, DO, DESCRIBE, EXPLAIN, USE, SET (except for SET GLOBAL|SET @@GLOBAL..), HELP, HANDLER, CHECK, ANALYZE, OPTIMIZE as well all transactional statements.
Further we also allow for CALL and please observe that ‘read-only mode’ is not enforced when executing a Stored Procedure or Function. It is also not enforced in the SJA – no matter whether launching an SJA-job from the GUI or from command-line. The SJA simply does not read this flag.
For the reasons above – and also because any user can easily turn the ‘read-only’ flag OFF – you should not consider this feature a ‘security feature’ (not a bullet-proof one, at least), but rather a ‘convenience feature’: With this flag ON, you will not accidentially (due to distraction, accidentially clicking with the mouse the wrong place or whatever) execute a statement that writes to the database. You are maybe not ‘fully secure’, but you are ‘safe’.
The ‘read-only’ feature is available in Professional, Enterprise and Ultimate editions of SQLyog.