PlanetMysql.ru — информация о СУБД MySQL

We have released SQLyog 9.2 GA with enhancements to the Data Search feature (and more).

Since we introduced the Data Search feature in SQLyog 9.1 we had a lot of positive responses – but also a few critical remarks that using the feature could cause unnecessary server load as well as unnecessarily long response times. Such scenario could arise when searching for a string in a BLOB column used for storing media files for instance. Or when searching all tables of a database when there was only need to search a few tables.

We have addressed this concern by adding filter options that let the user restrict the search to specific data types and to a subset of databases of a server, a subset of tables of a database or a subset of columns of a table.

Also we have added “+” and “-” operators for inclusive and exclusive exact match.

I would like to elaborate a little more on Data Search:

Data Search does not replace SQL, of course. It is a supplementing feature. It is in particular useful when your are searching for something you don’t know what exactly is and don’t know exactly where to find. And when you are just too lazy to write a long SQL statement. As we have posted here before you could consider the Data Search feature as a tool to ‘google your database’ (as google ‘advanced search’ operators are used). But a database has a hierachy and has datatypes what a document has not. So this filtering option is a logical database-related enhancement to the google ‘advanced search’ syntax used for documents.

Let us take an example: Suppose you want to find all instances of email addresses with a specific domain name in all your networked systems (on the Internet as well as Intranet). We have 3 such public systems (our Forums, Blog and FAQ) for our MySQL-related products alone  that are ‘standard applications’ that we did not code ourselves and thus do not know internals about very well. In all those systems people may comment or contact us. Add to this our non-public systems – like our CRM system and our support ticket system (based on our own web application IssueBurner that aggregates everything sent from and received to our contact email addresses to a database). As all the mentioned systems use a MySQL backend we will now easily be able to answer the question “Who have ever contacted us with a @like.this email address, when did it happen and what was the subject/matter?”. Simply because we can find the data in all systems. And anybody in our organization can do (provided that they have access) without knowing details about how and where the different applications store the information.

When we introduced Data Search in 9.1 I actually expected some comments that “this is a feature for amateurs and I do not intend to use it as I am familiar with SQL”. We did not get such comments till now! I think users already found out that it saves a lot of time.

Also in this release we are following up on the ‘Foreign Key lookup’ introduced in 9.0. This is now also functional from the RESULT tab in SQLyog.

And finally In this realease we added a ‘date picker’ GUI for managing DATE, DATETIME and TIMESTAMP columns as well as an option to clone a connection. Both were popular user requests for some time and have now been implemented.

See all details for this and other recent releases here.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

We are pleased to announce this new major release of SQLyog MySQL GUI.

The major enhancements with this release are:

* Information in tabbed interface can be reordered.
Just like you will find it in all modern browsers, TABs can now be reordered using drag’n’drop in the GUI. The option is available for connection tabs as well as Query/Query Builder/Schema Designer tabs.

* Fast and convenient data entry from the keyboard.
We have added ‘FORM view’ option (in addition to ‘GRID view’ and ‘TEXT view’ already available) for managing data in DATA and RESULT tabs. ‘FORM view’ will display one row at a time and is in particular convenient when entering data from the keyboard.

* Query Formatter
The SQLyog Query Formatter is now completely rewritten. In principle all types of SQL statements are now supported and all limitations with the old implementation are lifted.

* Several editor enhancements including:
The Editor now has a ‘folding option’. Multi-line code and comment blocks between bracket-pairs, BEGIN-END pairs, C-style comment pairs (/* and */), WHILE-END WHILE pairs, LOOP-END LOOP pairs, REPEAT-END REPEAT pairs and CASE-END CASE pairs can now be ‘folded’ in/out (ie: hidden or unhidden).

Add to that numerous stability fixes, GUI improvements and more. Read full details here.

We hope you will like this new version – and do not hesitate to contact us if you have comments, suggestions or whatever.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

We are pleased to announce the release of SQLyog – MySQL GUI 8.6 GA. This release adds functionalities requested by users for some time, and fixes a number of bugs. Most important enhancements:

User management has been updated with a brand-new interface, has been completely rewritten and also now fully communicates with the MySQL server the recommended way using GRANT and REVOKE syntax. We believe that with this release we have provided the best available ever GUI for MySQL User Management.

For users that prefer to work in a spreadsheet-like interface when filtering and sorting data the options to do this have been enhanced: There is now a ‘custom filter’ option to be used when filtering on a value that does not exist in the result set displayed – or even is not stored in the table at all. Additionally you may now define the substring to be filtered on in more flexible ways than before.

In the editor we added “parenthesis’es matching”. With complex statements (JOINs on derived tables, SUBQUERIES, statements with nested functions and similar) this will make it much easier to identify the structure of the statement. Just position the cursor after a parenthesis and the actual parenthesis and its match will highlight.

We have improved performance by optimizing code in code segments executed most frequently. Additionally we have deployed more debugging and performance measuring tools. This includes – but is not restricted to – moving our build environment to latest Visual Studio environment (2010 edition).

Note that with this release we have stopped supporting Windows 2000. It has for some time been increasingly difficult to continue this support. It is actually quite hard to find a recent system where Windows 2000 will run without errors and we have over the few last years spent quite a lot of effort fixing issues occurring only on this variant of Windows. We believe that the effort is better used ensuring optimal performance on recent and still supported Windows variants – not at least Windows 7, what fastly is taking the position of the dominating Windows variant. The move to Visual Studio 2010 shall be seen in this context. But of course XP, Vista (and the same generations of Windows server variants: 2003 and 2008) are still supported as well as Wine.

Links to Beta/RC release blogs with detailed information.
* http://www.webyog.com/blog/2010/08/17/sqlyog-mysql-gui-8-6-rc3-released/
* http://www.webyog.com/blog/2010/08/06/sqlyog-mysql-gui-8-6-rc2-released/
* http://www.webyog.com/blog/2010/08/06/sqlyog-mysql-gui-8-6-rc-released/
* http://www.webyog.com/blog/2010/08/03/sqlyog-mysql-gui-8-6-beta3-released/
* http://www.webyog.com/blog/2010/07/22/sqlyog-mysql-gui-8-6-beta2-released/
* http://www.webyog.com/blog/2010/07/20/sqlyog-mysql-gui-8-6-beta1-released/

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Hi,

We are pleased to announce the release of SQLyog – MySQL GUI 8.5 GA. Below are some pointers:

• As the title suggests this release comes with tabbed interface for different connections. We need not have to emphasize the usability of a tabbed interface vs. a windowed one. All web browsers have already demonstrated it to us. Now in SQLyog, you can switch between different connections in a snap! We didn’t forget to add keyboard shortcuts to jump from one tab to other. Most – if not all – shortcuts for tabs of a standard web browser would work with SQLyog. Multi-coloring of connection tabs & object browser pane adds to the ease of use. Chances of one executing queries in one server than the other by mistake would be rare as the brain would easily grasp the connection by it’s color. Demoed below is a typical setup of multi-colored tabs in a Web Developer’s PC:

• If you remember we added client side sorting of Result set data in SQLyog 8.4. With this release you can even filter the data of Result set on client side unlike Table Data where a query is fired to server for every sort or filter action. One more addition to view relevant data quickly.
• Who likes to right-click & open a file when you can just drag-and-drop? We bet you don’t. You can drag-and-drop files (SQL or Schema Design XML/Query Builder XML) directly into SQLyog.
• Whoever uses SQLyog for data entry or manipulation would love this feature to duplicate data in a record. Many a time all one needs is to change only few fields & retain the rest of the data from the preceding row. This feature would come handy in such cases. Tables with auto_increment columns are handed automatically.

This release also contains many more enhancements & bug fixes. Refer the following release notes for details:

• SQLyog 8.5 RC3 Release Notes
• SQLyog 8.5 RC2 Release Notes
• SQLyog 8.5 RC Release Notes
• SQLyog 8.5 beta3 Release Notes
• SQLyog 8.5 beta2 Release Notes
• SQLyog 8.5 beta1 Release Notes

SQLyog customers can download the latest installer from Webyog’s Customer Portal.
To evaluate SQLyog, please download the 30-day trial.

We are very excited about this release, and hope that you will like it. We would love to hear from you.

Cheers,
Team SQLyog

Hi,

SQLyog 8.4 happens to be a fairly major release with good number of features & enhancements. Listed below are some worth noting.

• May it be Query Profiler or Datatype Optimizer, SQLyog has grown beyond the definition of a GUI with these features with intelligence. One such feature that is being unveiled with this release is an option to find redundant indexes. You can find the redundant indexes in a Table with just a click of a button. If found, a ready query is generated to drop the redundant indexes. As you know eliminating redundant indexes improves INSERTs & UPDATEs and also saves hard-disk space.
• Scheduled Backups can be compressed.
• If you are one of those users who deal with databases having thousands of objects (tables, columns etc.) this release will definitely add to your productivity as auto-complete has been drastically improved for such databases.
• You can sort the data of Result set. The sorting is very fast as it is done at the client side unlike Table Data where a query is fired to server for every sort action.

Redundant Index Finder

This release also contains following enhancements:

• A file can be loaded to the tab from context menu.
• Added menu items (for exports and ‘copy to other..’) at table-level in Object Browser.
• Save dialog when closing a connection now has ’Yes to All’ and ‘No to All’ options.
• Added an option to send a mail alert if an error occurs while executing a ‘maintenance query’ from Notifications Services.

SQLyog customers can download the latest installer from Webyog’s Customer Portal.
To evaluate SQLyog, please download the 30-day trial.

We are very excited about this release, and hope that you will like it. We would love to hear from you.

Cheers,
Team SQLyog

PS: Redundant Index Finder is a feature of SQLyog Ultimate only.

Changes (as compared to 8.22) include:

Features:
* Added an option to define a ‘color code’ for a connection. The color will be used as background color in the Object Browser.
* A Query Builder session can now be saved and resumed.
* In Query Builder a table alias can be defined for any table by double-clicking the title bar of the table symbol.
* In RESULT tab results can now be retrieved page-wise. This is ON as default with this build with a defined LIMIT of 1000 rows. For a specific query user can change and for this specific query the setting is persistent across sessions. Also read ‘miscellaneous’ paragraph below.
* Added a context menu to Query Builder canvas.

Bug Fixes:
* Deleting a user would leave non-global privileges orphaned in the ‘mysql’ database. Now we use DELETE USER syntax if server supports.
* Also using EDIT USER dialogue to change host or user specifier for a user would not move non-global privileges. We have split the old ALTER USER dialogue into two: a EDIT USER and RENAME USER dialogue. The latter will use RENAME USER syntax if server supports.
* On Wine Data Sync could generate a malformed XML-string what would case Data Sync to abort.
* Fixed an issue where SSH-tunneling failed with public/private key authentication. Technically the fix is in the PLINK binary shipped with SQLyog.
* SJA failed to send notification mails if Yahoo SMTP servers were used. Note that the fix disables encryption option with Yahoo SMTP servers – but it won’t work anyway due to a non-standard SMTP implementation server-side.
* When importing data from a Universe ODBC-source string data could be truncated.
* The fix in 8.22 for the issue that horizontal scrollbar in GRID would sometime not appear was not complete. It could still happen.
* SQLyog will now trim trailing whitespaces in Connection Manager and Create object dialogs to avoid MySQL Errors..
* Opening a file from ‘recent files’ list could crash SQLyog if a Query Builder or Schema Designer tab was selected and the file specified was not a valid XML file for that tab. This bug was introduced in beta 1.
* When calling a Stored Procedure with more than one SELECT statement from ‘Notifications Services’ only one result set was sent by mail.
* The sja.log file had no line-breaks between what was recorded for two jobs.
* On multi-monitor system resizable dialogues could open on the wrong monitor. New implementation is like this: on multi-monitor systems main program dialogue and ‘first child dialogue’ (example: ALTER TABLE) will open where they were closed (if possible), second and higher child dialogues (example: table advanced properties) will always open on top of its ‘parent’ dialogue. Non-resizable dialogues (such as confirmation boxes) will always open on top of their ‘parent’.
* With multiple SSH-tunnelled connections open stopping and re-executing queries in multiple connections in a fast manner could crash SQLyog.
* If more than one comment occurred before a SELECT statement in the editor, the statement was not identified as a SELECT statement by the Query Profiler and the Query Profiler TAB would not display.
* We did not validate client-side if user checked atoincrement option for a bit column with Create/Alter table dialog.
* If an error occurred while renaming a trigger then trigger was lost as SQLyog was not recreating it back.
* Small GUI fixes.

Miscellaneous:
* The default LIMIT setting for DATA tab has been removed. The setting is not required since we introduced table-level persistence for number of rows displayed. The default for new tables that have not been opened before is 50 – but when user changes the value and next ‘refresh’es SQLyog will save the LIMIT for that particular table persistently across sessions. This in combination with page-wise display in RESULT tab results in a more uniform User Interface for DATA and RESULT tabs.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Dear MariaDB users,

MariaDB 5.1.42, a new branch of the MySQL database which includes all major open source storage engines, myriad bug fixes, and many community patches, has been released. We are very proud to have made our first final release, and we encourage you to test it out and use it on your systems.

For an overview of what’s new in MariaDB 5.1.42, please check out the release notes.

For information on installing MariaDB 5.1.42 on new servers or upgrading to MariaDB 5.1.42 from previous releases, please check out the installation guide.

MariaDB is available in source and binary form for a variety of platforms and is available from the download pages.

It is also our pleasure to announce that we have a partnership with Webyog to offer their tools for trial and at a discounted rate if purchased within 30 days. Find out more at: Download – SQLyog MySQL Fronted, MONyog MySQL Monitoring Tool or via the software partner downloads.

We welcome and appreciate your feedback, bug reports, bug fixes, patches, and participation on our mailing list. Find out more about working with the community.

Enjoy!

Related posts:

1. MySQL on Leopard OS X 10.5 PrefPane fixed!
2. MySQL with yaSSL vulnerability
3. MySQL Connector/PHP for MySQL 5.0.24 and PHP 5.1.5 released

Dear MariaDB users,

MariaDB 5.1.42, a new branch of the MySQL database which includes all major open source storage engines, myriad bug fixes, and many community patches, has been released. We are very proud to have made our first final release, and we encourage you to test it out and use it on your systems.

For an overview of what’s new in MariaDB 5.1.42, please check out the release notes.

For information on installing MariaDB 5.1.42 on new servers or upgrading to MariaDB 5.1.42 from previous releases, please check out the installation guide.

MariaDB is available in source and binary form for a variety of platforms and is available from the download pages.

It is also our pleasure to announce that we have a partnership with Webyog to offer their tools for trial and at a discounted rate if purchased within 30 days. Find out more at: Download – SQLyog MySQL Fronted, MONyog MySQL Monitoring Tool or via the software partner downloads.

We welcome and appreciate your feedback, bug reports, bug fixes, patches, and participation on our mailing list. Find out more about working with the community.

Enjoy!

Related posts:

1. MySQL on Leopard OS X 10.5 PrefPane fixed!
2. MySQL with yaSSL vulnerability
3. MySQL Connector/PHP for MySQL 5.0.24 and PHP 5.1.5 released

Changes (as compared to 8.2) include:

Features:
* Now SJA will also send mail alert if job aborted due to MySQL error. Before it was only internal SJA error.
* The local port used by SSH-tunneling will now be selected automatically. This will avoid conflicts in case multiple programs use SSH. Also with Data Sync from command-line/scheduler it was possible to use same port for both connections what would effectively sync a server with itself.
* Caption for ‘Parse’ button in Notification Services Wizard was changed to make it clear that it will actually execute the statement(s) entered. There is no way to let the server parse a statement except for executing it.
* Connection windows for SSH connections will now list SSH host details in the title bar.
* Tooltips for an icon will now list the keyboard shortcut performing same action.
* The option to display ‘all’ versus a ‘LIMIT’ed set of rows in DATA tab is now table-specific and saved across sessions (note that – similar to the ‘column width persistence’ feature – connection parameters are not using for identifying a table; only the database name and the table name are).
* Objects in an Object Browser node is now sorted case-insensitive.

Bug Fixes:
* Continuously clicking the ‘Calculate’ button in Schema Optimizer in a fast manner could crash SQLyog.
* The keyword.db file (used by auto-complete and syntax highlighting) is now read only. Various validators for Windows7-compatibility would report that SQLyog wrote to “Program Files” folder at runtime (what it did not).
* When copying to clipboard an out of memory error could occur also when there was enough memory.
* The table menu will now indicate what storage engine is currently used for the table.
* Autocomplete and syntax highlighting did not recognize keywords archive, blackhole, federated, example, maria, pbxt, federatedx, falcon and mrg_myisam.
* Notifications Services/’Send Query to Email address’ option did not send a mail if an error occurred. Now a mail listing the error will be sent.
* We did not validate client-side if user specified a default value for an auto-increment column (what is invalid with MySQL).
* In DATA and RESULT tab the context menu was only working from GRID-cells. Now it also does from GRID headers and ‘whitespace’ in the tabs.
* Updating a ’TIMESTAMP on update CURRENT_TIMESTAMP’ had no effect (the particular column was not listed in the UPDATE-statement sent by SQLyog). This was a necessary restriction before 8.13 but since we – from 8.13 – only list columns that have actually been edited by user, we can now lift this restriction.
* Import External Data – TRIGGERS could fail to update a SQL Server (n)varchar if it contained an empty string.
* If user had selected to save SSH-password locally and later changed the password, the new password was not saved – unless clicking ’save’ button in connection manager interface.
* When importing an external script with no explicit SET NAMES on top, SET NAMES latin1 was executed by SQLyog. Now we won’t do this – and server default charset will have effect for the import in such case.
* Autocomplete did not handle identifiers with the ‘_’ character correctly what could result in too many matches when matching the database with a pattern in editor containing such character.
* Other small GUI fixes.

Miscellaneous:
* This release ships with an updated tunneler file for HTTP-tunneling. In the old tunneler file functions were used that are depreciated in PHP 5.3x.
* The ‘Objects’ menu was renamed to ‘Others’.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php

Changes (as compared to 8.14) include:

Features:
* Added an option to execute SHOW WARNINGS automatically if the ‘warning-count’ is not 0. The output will appear in MESSAGES tab. Note: this is not implemented for HTTP-tunneling.
* Improved the memory handling in GRIDS with BLOB/TEXT columns. This fixes some slugginess when scrolling a GRID containing such data.

Bug Fixes::
* A dump containing VIEWs created on an early 5.0-server could fail to restore on recent servers. The underlying reason is a bug with the ‘default’ column in the output of SHOW FULL FIELDS on the early 5.0 servers. But we can avoid using this information and this is what we did now.
* Copy database/table from a 3.x or 4.0 server to a more recent server failed with column names containing special characters.
* If a sqlyog.ini files exists in installation folder it should be copied to ‘AppData’ folder. This is required for upgrading from versions before 6.06. However with latest releases an empty file was created in ‘AppData’.
* The ‘Import External Data Tool’ could truncate strings when importing data from a 4D database. It is actually a bug in the 4D ODBC driver but we found a workaround.
* SSL-connections failed if authentication keys were created with cipher option.
* SQL-exports generated INSERTS for MERGE and FEDERATED tables.
* In INFO-tab/text-mode we will now not highlight ’string literals’. A comment with an odd number of quotes would make following lines display with ’string literal’ highlighting/coloring.
* When connected with SSH-tunneling to a Windows machine with Cygwin SSHD the bash.exe process created for each connection did not close again.
* CREATE TABLE .. advanced options did not set some create-options to ‘default’.
* Execution of some queries would be slow with Query profiler/EXPLAIN extended selected. Most important queries with a UNION were affected. Technically it was an issue with the Query Formatter code and how it ‘hooked’ into the program. This bug was introduced in 8.0.
* Windows Vista and higher could warn that SQLyog was not properly installed due to lack of an Application Manifest. It was false alarm but now such Manifest is included with the installer.

Miscellaneous:
* Functionality change: Before this release we stripped out the database name from Stored Program and View SQL-code when generating SQL-dumps and when copying a database to another host. Also Schema Sync did with VIEWs. This was in order to make it easy to import/copy to another database.  However with tables named identical to the database and when database names was a substring of a table name it failed sometimes.  We realize now that SQL code inside Stored Programs and Views may be so complex that parsing for the database name and stripping it is not safe.  With this release we have stopped this ’stripping’ and Stored Programs and Views will be dumped by SQLyog identically to what  ‘mysqldump’ does.

Downloads: http://webyog.com/en/downloads.php
Purchase: http://webyog.com/en/buy.php