development - SQLyog Ultimate

릴리스 노트: With the MariaDB server, it is now possible to create a ‘Key’ index on a virtual column using the GUI. Emojis will be displayed as is in the ‘Table Data/Result’ tab, ‘Scheduled Backups’, ‘Copy Database To Different Host/Database’ on setting the character set to ‘utf8mb4’ in the ‘Init Command(s)’ ...

고객 리뷰: 5 China ...

고객 리뷰: 5 Korea, Republic Of ...

릴리스 노트: Upgraded the PLINK executable bundled with SQLyog to PuTTY/PLINK v0.77, to support private keys generated in the PPK version 3 file format. With Azure DB, SQLyog returned an error “unknown thread id” on stopping the query execution. With Azure DB, SQLyog crashed when killing the query from another ...

고객 리뷰: 5 Korea, Republic Of ...

설명: Front Ends and MySQL GUI tools in a single intuitive interface. SQLyog is a fast, easy to use and compact graphical tool for managing your MySQL databases. SQLyog Ultimate was developed for all who use ...

릴리스 노트: Updates ‘User Manager’ GUI to support newly added privileges in MariaDB v10.5. Updated the ‘User Manager’ GUI to support newly added privileges in MariaDB v10.5. Changes in SQLyog MySQL13.1.9 GUI include the following bug fixes: SQLyog returned an error when setting user server resources like ...

고객 리뷰: 5 France ...

릴리스 노트: With MariaDB System-Versioned tables, SQLyog was hanging when clicking on SQL Preview in the Alter table wizard. Indexes were not being displayed with MariaDB System-Versioned tables. In some cases, LOAD DATA LOCAL INFILE query failed to be executed from the Query Editor. Schema Sync tool generated ...

고객 리뷰: 5 France ...

릴리스 노트: Unable to connect to a MySQL server using SSL when the client doesn’t provide a CA Certificate file, prior to version 10.4. When Editing a MySQL user password, the MariaDB server version was not working. The Calculate Optimal Datatypes in the Info tab returned syntax error for MySQL version 8 and ...

릴리스 노트: Adds option to specify the authentication plugin while creating/altering the user. An option has been added to specify the authentication plugin while creating/altering the user. This option is available for MySQL 5.7+ and MariaDB 10.4+ servers. Now, it is possible to create invisible and ...

고객 리뷰: 5 Korea, Republic Of ...

릴리스 노트: Upgraded Microsoft Visual Studio build environment and OpenSSL and SQLite libraries for improved security and performance. Added an option to the ‘Scheduler and Reporting tool’ to attach query result(s) as CSV files. Errors returned from queries are now logged to HISTORY tab. Added an option to ...

릴리스 노트: Maintenance release upgrades the MariaDB Connector/C to version 2.3.3. Upgrades the MariaDB Connector/C to version 2.3.3 (current) which resolves incorrect timeouts on some environments. ...

릴리스 노트: Introduces a new feature- REGEX search in Object Browser, plus bug fixes. Search function in Object Browser now supports regular expressions. 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 ...

릴리스 노트: Introduces a long requested feature, HEX-dumping of binary data. 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 SQLyog doesn’t allow ...

릴리스 노트: Introduces a new major feature- ‘read-only’ connections – as well as Kerberos authentication support and a few bug fixes. Updates in v12.4.0 Features 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 ...

릴리스 노트: Bug fix release. Updates in v12.3.3 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 ...

릴리스 노트: Includes minor bug fixes. Updates in v12.3.2 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. ...