This release fixes a rare crash as well as a regression bug introduced in 13.1.0.
Bug Fixes:
–Fixed a regression bug introduced in 13.1.0, an error was returned on adding or editing the data in the ‘Result’ tab. The same steps also caused SQLyog to crash sometimes. This is fixed now.
The post SQLyog MySQL GUI 13.1.1 Released appeared first on SQLyog Blog.
Since April 19th, when MySQL 8.0 became Generally Available (GA), the MySQL community has been abuzz with excitement over all of the new features and improvements. Many of new features were improvements to performance or monitoring, while others were specifically related to replication. We reviewed Replication Performance Enhancements in MySQL 8 recently. Today’s blog will describe how to set up a basic master-slave configuration with MySQL, using two servers on a single machine.
Replication Defined
MySQL replication is a process in which data from one MySQL database server (the master) is copied automatically to one or more MySQL database servers (the slaves). In the case of multiple slaves, these are usually referred to as a slave cluster. Replication should not to be confused with backup operations. Whereas the aim of backups is to protect the data and/or data structure, the role of replication is typically to spread …
[Read more]Important notice: with this release we have changed registration keys. Please have your new key available when upgrading. As usual registered users will get it from our Customer Portal.
This new release of SQLyog has a lot of internal changes: our Visual Studio build environment was upgraded from the old 2010 version, we used before – what required a lot of code changes, actually – and also OpenSSL and SQLite libraries were upgraded for improved security and performance. Additionally we have added features and fixed bugs with this release.
Also note that the upgrade of Visual Studio means that Windows older than Vista (ie. WinXP/2003) and Wine older than version 2.0 are not supported any more.
Changes as compared to MySQL GUI 12.5.1 include:
Features:
…[Read more]Every MySQL database programmer should learn and apply the newly added MariaDB and MySQL Window Functions and Common Table Expressions(CTEs) in their daily work. Both CTEs and window functions enable easy solutions to many query challenges that in prior releases have been difficult and sometimes impossible to surmount. Mastering these features opens the door to query solutions that are more robust, execute faster, and are easier to maintain over time than prior solutions using older techniques.
In our last blog we compared User Roles in MySQL 8 vs. MariaDB. Today, we will here compare Window Functions and Common Table Expressions in both databases.
Window Functions
While all database administrators are familiar with aggregate functions like COUNT(), SUM(), and AVG(), far less people make use of window functions in their queries. Unlike aggregate functions, which operate on an entire table, window …
[Read more]
In our last blog, we had a look at MySQL 8 and mentioned new features available here. However, some of those features are already in MariaDB and have been for a while. We will here compare database roles in both server dialects.
The Purpose of Database Roles
It’s common for numerous users within an organization to share the same database privileges. A role bundles a number of privileges together so that the DBA can set the privileges for a group of users all at once, rather than having to set each user’s privileges individually.
With shared applications, it is not uncommon for multiple users to share the same user account. The drawback to this arrangement is that there is no way to see which actual user was responsible for which action.
Roles make managing this much easier. For example, there …
[Read more]This maintenance release introduces a long requested feature – HEX-dumping of binary data – and adds a number of non-critical bug fixes.
Changes as compared to MySQL GUI 12.4 include:
Features:
* 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 redrawn 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 …
This is a bug-fix release. Please refer details below.
Changes as compared to SQLyog MySQL GUI 12.3.2 include:
Bug Fixes:
* Fixed an issue where Import External Data -jobs failed to
authenticate SMTP.
* The sja.log would record syntax errors on recent servers if
Scheduled Backup was running with ‘Flush Master’ option.
The generated backup file was OK. ‘Flush Master’ was deprecated
in MySQL 5.6 and replaced with ‘Reset Master’. We now
use ‘Reset Master’ with such servers.
* In email settings of Import External Data wizard it was
possible to leave the subject empty.
* When re-ordering columns, an ON UPDATE -clause could be lost in
specific cases.
* Fixed cases where index-level comments were not saved and …
This release fixes a few issues in the new GUI transactions supporting with specific and uncommon server settings.
Changes as compared to SQLyog MySQL GUI 12.3.1 include:
Bug Fixes:
* If an INIT_CONNECT setting in server configuration specified
SET AUTOCOMMIT = 0 and global AUTOCOMMIT was 1 (or non-existent
as in MySQL 4.1 and 5.0), the ‘transactions’ menu in SQLyog would
incorrectly display AUTOCOMMIT as 1 after connection.
* Same code change as above also fixes a crash that could occur
with 4.1 servers.
* Transactions support would fail to initialize with servers
running global ANSI mode. SQLyog will not work in ANSI mode but
connection and initialization should work, so that user as the
first step may specify a supported session sql_mode (from the
editor or from ‘advanced’ tab in connection …
This release fixes a rare crash as well as a regression bug introduced in 12.3.0.
Changes as compared to SQLyog MySQL GUI 12.3.0 include:
Bug Fixes:
* 12.3.0 introduced a slowness when displaying the saved
connections list with a large no. (100+) of saved connections.
This is fixed now.
* Fixed a rare crash occurring sometimes when typing in the
editor inside an invalid query longer than 128 characters.
Auto-complete was at fault.
Downloads: https://www.webyog.com/product/downloads
Purchase: https://www.webyog.com/shop
The post SQLyog MySQL GUI 12.3.1 Released …
[Read more]This release introduces a new major feature – GUI transaction support – as well as some minor features and bug fixes.
Changes as compared to MySQL GUI 12.2.6 include:
Features:
* GUI transactions support. This new feature is available in
Enterprise and Ultimate editions. Also please see note
below.
* Added a tooltip on column headers in Data tab informing
about column name, column type and length.
In Result tab the tooltip will display column name only, as
the result returned by MySQL does not have information of
storage type details.
* Added GUI support for index-level comments in CREATE/ALTER
TABLE.
Bug Fixes:
* Fixed an issue where GUI could ‘hang’ when executing queries
with very large subqueries.
* Fixed an issue with the …