Here at Monitis, we’re on a mission to not only build the best product but also, at the same time, make it more user-friendly. We listen to your feedback and suggestions and take various steps to improve our services, tools and features to make YOUR life easier. In any given week, you can see a new feature or update in your Monitis dashboard. Here’s some of the stuff we’ve added since our last newsletter, three months ago. Stay-up-to-date and see all that we have to offer by reading about all our changes below:

(more…)

The MySQL Developer Tools team is pleased to announce the availability of the third beta release of MySQL Workbench 6.0. MySQL Workbench 6.0 is the new major update of the Development and Administration tool for MySQL. This release includes almost 200 bug fixes (~40 since 6.0.3), 30 new features and a new redesigned UI. As a beta, this release is not suitable for production use.  Please test and file your bug reports at http://bugs.mysql.com

As always, MySQL Workbench is natively available on Windows, Mac, Linux.

Improvements in MySQL Workbench 6.0:

• a new redesigned Home screen
• the SQL Editor and Server Administration UIs were merged into a single connection specific interface, allowing for quick access to administration features while simplifying the location of specific features
• improved model Synchronization, lets you …

With the first beta of MySQL Workbench 6.0 just released, we’ll go through the list of improvements we’ve made since 5.2.47

New Home Screen

The Home screen went through a renovation and now has a modernized look. As part of the SQL Editor and Administration GUI unification, there’s now a single list for MySQL connections. Recently opened model files and other major features are also accessible from it.

You can organize different connections into “folders” by right clicking on a connection and selecting “Move to Group…” in the context menu.

New server connections can be added by clicking the + button next to the MySQL Connections heading. By clicking the Configure Remote Management… button in the new connection setup dialog, you can add server management capabilities to the connection. As before, SSH access with “sudo” is needed for remote management.

The MySQL Developer Tools team is pleased to announce the availability of the first beta release of MySQL Workbench 6.0. MySQL Workbench 6.0 is the new major update of the Development and Administration tool for MySQL. This release includes over 100 bug fixes, 30 new features and a new redesigned UI. As a beta, this release is not suitable for production use.  Please test and file your bug reports at http://bugs.mysql.com

As always, MySQL Workbench is natively available on Windows, Mac, Linux.

Improvements in MySQL Workbench 6.0:

• a new redesigned Home screen
• the SQL Editor and Server Administration UIs were merged into a single connection specific interface, allowing for quick access to administration features while simplifying the location of specific features
• improved model Synchronization, lets you compare and update your …

One of the best new ideas in my eyes came from quelbs. Using an integer column for storing UNIX timestamp values is a wide spread approach in the world of web development. For example in a Typo3 database, all date/time handling is done with UNIX timestamps. Unfortunately, for MySQL this is of course a normal integer value, with no meaning of being a date/time value.

Now, HeidiSQL allows the user to explicitly set a column to "This is a UNIX timestamp" via right click menu. Once activated, integers are internally converted to and displayed as human readable date/time values. Editing such values also uses the inplace editor for date values.

One of the best new ideas in my eyes came from quelbs. Using an integer column for storing UNIX timestamp values is a wide spread approach in the world of web development. For example in a Typo3 database, all date/time handling is done with UNIX timestamps. Unfortunately, for MySQL this is of course a normal integer value, with no meaning of being a date/time value.

Now, HeidiSQL allows the user to explicitly set a column to "This is a UNIX timestamp" via right click menu. Once activated, integers are internally converted to and displayed as human readable date/time values. Editing such values also uses the inplace editor for date values.

One of the best new ideas in my eyes came from quelbs. Using an integer column for storing UNIX timestamp values is a wide spread approach in the world of web development. For example in a Typo3 database, all date/time handling is done with UNIX timestamps. Unfortunately, for MySQL this is of course a normal integer value, with no meaning of being a date/time value.

Now, HeidiSQL allows the user to explicitly set a column to "This is a UNIX timestamp" via right click menu. Once activated, integers are internally converted to and displayed as human readable date/time values. Editing such values also uses the inplace editor for date values.

One of the best new ideas in my eyes came from quelbs. Using an integer column for storing UNIX timestamp values is a wide spread approach in the world of web development. For example in a Typo3 database, all date/time handling is done with UNIX timestamps. Unfortunately, for MySQL this is of course a normal integer value, with no meaning of being a date/time value.

Now, HeidiSQL allows the user to explicitly set a column to "This is a UNIX timestamp" via right click menu. Once activated, integers are internally converted to and displayed as human readable date/time values. Editing such values also uses the inplace editor for date values.

The MySQL Workbench team has been a little quiet for the past few months, but that’s because we’ve been busy working on an exciting new version. Read more about it in Tomas’ blog

The latest update (v 3.0.9) includes a feature for excluding queries from statistics. To make Jet Profiler ignore certain queries, you need to edit the original query in the application code.

Start the query with /*jp-ignore*/ (no spaces), for example "/*jp-ignore*/ SELECT ... FROM ..."

This will prevent the query from showing up in Top Queries and the other tabs. The query will, however, still affect general preset statistics (such as number of threads running and threads busy). Also make sure that your mysql client library preserves comments - some libraries including the mysql command line client removes comments by default.


2 Comments