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

New updates in Jet Profiler 3 include the following improvements:

• Improved multiple instance handling.
• Faster data retrieval.
• New, more efficient MySQL JDBC driver from SkySQL / MariaDB.
• Top Schemas is now available in the free version by default.
• Faster startup time.
• Bug fixes.

To read the full changelog, click here.


Comments

There are a lot of great articles and reviews written about Jet Profiler and we think it's about time they get a bit of attention. Here's a great article, Hands on with Jet Profiler, that was published yesterday by a company called Monitis.

A few highlights from the article:

"I recorded continuously for more than 2 days and Jet Profiler was as responsive at the end as it was at the start. Only the switching between the graphs seemed to get slower when there is more recorded data. But that seems to be logical. Let’s do the math again here to establish the number of queries dealt with over 2 days i.e. 2 days = 48 hours or 2,880 minutes. And with 12,000 queries a minute we have a staggering 34,560,000 queries recorded in those 2 days."

"Without going through all the great features of Jet …

New Version of Data Traffic Manager Supports Infinite Application Scalability, a Sleek New Look and Easier-than-Ever Deployment BOSTON – February 12, 2013 — ScaleBase, the company that keeps next gen apps and business-critical databases up-and-running, just released Data Traffic Manager 2.0.  It’s the only database scalability software that solves the three biggest challenges next-gen apps face [...] Read More