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

We’re proud to announce the next release of MySQL Workbench, version 5.2.30. This is a maintenance release focusing on general product improvement and usability. In addition to that, we have added a small set of Text-Formatting-Plugins to the SQL Editor to help format/structure your SQL Queries.

As always, we want to thank everyone for the great feedback we have received. This helps us to continuously improve the functionality and stability of MySQL Workbench – we appreciate all your ideas for improving MySQL Workbench.  Please keep sending us your ideas!

About the Query-Formatter

In the Edit->Format menu of Workbench’s SQL Editor you will see a set of functions that assist in reformatting your SQL Queries, for example “Beautify Query”, “UPCASE Keywords”, etc.

MySQL Workbench 5.2 GA

• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)

Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

To get started quickly, please take a look at this short tutorial.

MySQL Workbench 5.2 RC Tutorial

http://wb.mysql.com/?p=406

Workbench Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/index.html

In addition to the new Query/SQL Development and Administration modules, version 5.2 features improved stability and performance – especially in Windows, where OpenGL support has been enhanced and the UI was optimized to offer better responsiveness.
This release also includes improvements to the scripting capabilities of the SQL Editor. You can read more about it in

http://wb.mysql.com/workbench/doc/

For a detailed list of resolved issues, see the change log.

http://dev.mysql.com/doc/workbench/en/wb-change-history.html

If you need any additional info or help please get in touch with us.

Post in our forums, leave comments on our blog pages or if you want to talk to us directly you can visit us on our IRC channel #workbench on irc.freenode.net.

- The MySQL Workbench Team

Go to devart.uservoice.com and share your ideas about new features you want to see in dbForge Studio for MySQL. There you may vote for features that are already in our roadmap, and they will have higher priority in our plans, or you may suggest your own features, and if they will get enough votes, we will include them to the roadmap. Your opinion helps us to make our MySQL GUI Client better and more useful for you.

We have already started implementing of the following features:

  Export data of the several tables at once

Data Export Wizard will allow to select multiple tables to export. Database Explorer will allow quick export from several tables selected with Ctrl+Click.

  Lookup editor for data columns with foreign key

For columns included in foreign key constraint Data Editor will allow to view and pick master records from popup editor.

  Edit result set of a query with JOIN

Data Editor with allow to edit result set of a SELECT statement containing JOIN clause. Data Editor toolbar will contain a combo-box that allows to chose table to edit. This table columns are highlighted and all other columns are grayed.

  Server-side filtering in Data Editor

Allows to get correct filtering results when only a portion of data is fetched from server (e.g. when paginal mode is on).

  Server-side sorting in Data Editor

Allow to view data in correct order even if only part of it is fetched from server (e.g. in paginal mode).

  Master-detail data browser

Allows to view data from 2 or more tables connected with one-to-many relationship (physical or logical). We plan to implement separate document with two views: Diagram and Data. Diagram view allows to build master-detail relationships visually (akin to Query Builder). Data view shows multiple result data sets.

The following features are on our roadmap:

  MySQL object dependency lister

Allows to Right-Click on an object and ‘auto-object search’ current schema for where this is used.

  Command line interface for Data Import and Data Export

Support of command line interface for importing/exporting data from/to Excel, CSV, XML, DBF, etc.

  Import data from multiple files at once

Data Import Wizard will allow to select multiple sources to import data.

  Draw charts from data editor

Wizard to create charts from data editor. Ability to draw chart automatically from pivot grid.

We’re proud to announce the next release of MySQL Workbench, version 5.2.29. This maintenance release focuses on general product improvement and usability.

As always, we want to thank everyone for the great feedback we have received. This helps us to continuously improve and extend the functionality and stability of MySQL Workbench – please keep up on approaching us with any ideas to develop our product even further.

New Workbench 5.2.29 Preference/Feature

Say you have been working on a model for hours in Workbench, and you haven’t saved in the last 90 minutes, suddenly the power goes out (or some other force majeure). Now with 5.2.29, if Workbench unexpectedly quits during modeling, the model you were working on will be restored to the last auto-saved version the next time you open that model.
As always, please remember to save and version your models regularly.
Also – you can change the value of Auto-Save Model Interval from its 5 minutes – go to Edit->Preferences and change within the General tab.

MySQL Workbench 5.2 GA

• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)

Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

To get started quickly, please take a look at this short tutorial.

MySQL Workbench 5.2 RC Tutorial

http://wb.mysql.com/?p=406

Workbench Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/index.html

In addition to the new Query/SQL Development and Administration modules, version 5.2 features improved stability and performance – especially in Windows, where OpenGL support has been enhanced and the UI was optimized to offer better responsiveness.
This release also includes improvements to the scripting capabilities of the SQL Editor. You can read more about it in

http://wb.mysql.com/workbench/doc/

For a detailed list of resolved issues, see the change log.

http://dev.mysql.com/doc/workbench/en/wb-change-history.html

If you need any additional info or help please get in touch with us.

Post in our forums, leave comments on our blog pages or if you want to talk to us directly you can visit us on our IRC channel #workbench on irc.freenode.net.

- The MySQL Workbench Team

We’re proud to announce the next release of MySQL Workbench, version 5.2.28. This maintenance release features improvements to the Workbench scripting Shell as well as various fixes.

Enhancements to the Workbench 5.2.28 Scripting Shell makes development and usage of Workbench Scripts and Plug-ins easier by

• Providing a new workbench shell scripting file browser
• Allowing users to more easily create/edit/save/execute Workbench python and lua scripts
• Including Handy Workbench “Scripting” snippets that can easily be executed or copied.
• Adding a new script results output panel

For more on Workbench Scripting and Plug-in development see

http://wb.mysql.com/?page_id=664

As always, we want to thank everyone for the great feedback we have received. This helps us to continuously improve and extend the functionality and stability of MySQL Workbench – please keep up on approaching us with any ideas to develop our product even further.

MySQL Workbench 5.2 GA

• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)

Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

To get started quickly, please take a look at this short tutorial.

MySQL Workbench 5.2 RC Tutorial

http://wb.mysql.com/?p=406

Workbench Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/index.html

In addition to the new Query/SQL Development and Administration modules, version 5.2 features improved stability and performance – especially in Windows, where OpenGL support has been enhanced and the UI was optimized to offer better responsiveness.
This release also includes improvements to the scripting capabilities of the SQL Editor. You can read more about it in

http://wb.mysql.com/workbench/doc/

For a detailed list of resolved issues, see the change log.

http://dev.mysql.com/doc/workbench/en/wb-change-history.html

If you need any additional info or help please get in touch with us.

Post in our forums, leave comments on our blog pages or if you want to talk to us directly you can visit us on our IRC channel #workbench onirc.freenode.net.

- The MySQL Workbench Team

Devart made it to the final of 2010 DevProConnections Community Choice Awards. The awards recognize the best products and services in the industry by a community vote.

Devart has been nominated in 4 categories of 2010 DevProConnections Community Choice Awards!

Nominated products:

• Best Add-In Product – Entity Developer
• Best Component Set – dotConnect for Oracle
• Best IDE Product – dbForge Studio for MySQL
• Best Free Tool – CodeCompare

If some of your favorite products are in that list, please visit: http://www.surveymonkey.com/s/DEVCommChoiceFinalVoting and cast your vote for your favorite Devart products.

Note: Voting ends on September 21, 2010.

Thank you and best wishes,
The Devart Team
www.devart.com

We’re proud to announce the next release of MySQL Workbench, version 5.2.27. This is the second maintenance release for 5.2 GA (Generally Available). This maintenance release does not introduce any new features, but focuses on general product improvement and usability.  We hope you will make MySQL Workbench your preferred tool for Design, Development, and Administration of your MySQL database applications.

As always, we want to thank everyone for the great feedback we have received. This helps us to continuously improve and extend the functionality and stability of MySQL Workbench – please keep up on approaching us with any ideas to develop our product even further.

MySQL Workbench 5.2 GA

• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)

Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

To get started quickly, please take a look at this short tutorial.

MySQL Workbench 5.2 RC Tutorial

http://wb.mysql.com/?p=406

Workbench Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/index.html

In addition to the new Query/SQL Development and Administration modules, version 5.2 features improved stability and performance – especially in Windows, where OpenGL support has been enhanced and the UI was optimized to offer better responsiveness.
This release also includes improvements to the scripting capabilities of the SQL Editor. You can read more about it in

http://wb.mysql.com/workbench/doc/

For a detailed list of resolved issues, see the change log.

http://dev.mysql.com/doc/workbench/en/wb-change-history.html

If you need any additional info or help please get in touch with us.

Post in our forums, leave comments on our blog pages or if you want to talk to us directly you can visit us on our IRC channel #workbench on irc.freenode.net.

- The MySQL Workbench Team

The basic data structure that powers databases is called a B-tree. This is where you actually store the user’s data. B-trees are great because you can put huge amounts of data in them and access remains fast. In fact, the naive strategy of putting a whole data set into one B-Tree doesn’t break down because of access time. It does, however, break down when you try to support a multiaccess paradigm.

Six years ago, multiaccess was nice. Now that processors have multiple cores, it’s crucial. Four cores fighting over one B-tree means a lot of wasted processor time. In a multiaccess scheme, different cores can concurrently access data. This gets tricky. You can go looking for a piece of data only to find that someone has moved it since you started; that’s trouble: for all you know it was deleted. You could start the search over, but without guarantees—maybe you’ll get unlucky and it will be plucked out from under you again. How do you know when to give up? Your database is now blazingly fast, but also broken. We handle this with a locking scheme.

With a locking scheme, you gain the ability to say: “Okay, I’m going to go look for this piece of data, no one else is allowed to touch it.” If someone else wants to get at that piece of data before you’re done—they have to wait. The database is fixed, but it’s not quite as blazingly fast as it used to be. The problem is that sometimes cores have to wait for data, and while they wait they’re just twiddling their thumbs. There isn’t a good way to prevent these waits, but we can put that time toward something productive.

The problem isn’t the waiting, it’s the lack of things to do during that time. The solution is to slice up our B-Tree into several smaller B-Trees. Every possible key has one and only one slice that it can ever be stored in. We do this with hashing. Now even if a core locks up an entire B-Tree, you can still do work in the intervening time.

Now that we support multiple slices, the question is: how many slices do we actually want? There are downsides to both extremes: too many slices and the efficiency of the B-Tree structure is underused, too few and CPUs are underused. At RethinkDB we’ve found experimentally that 4 is a sufficiently high value. The quick back-of-the-envelope calculation is that an unsliced B-Tree will defy computation about of the time. That translates to an hour of wasted CPU time every 2 days. This waste falls off very sharply with our innovation: 2 slices are busy: (just of the time) and 4 slices are busy or . At which point it will take you 700 years to waste an hour of CPU time. That’s a number we can live with.

We’re happy to announce the release of MySQL Workbench 5.2.26. This is the first maintenance release for 5.2 GA (Generally Available). We have fixed a number of bugs and made some improvements under the hood. We hope you will make MySQL Workbench your preferred tool for Design, Development, and Administration of your MySQL database applications.

We want to thank everyone for the great feedback we have received. This helps us to continuously improve and extend the functionality and stability of MySQL Workbench – please keep up on approaching us with any ideas to develop our product even further.

MySQL Workbench 5.2 GA

• Data Modeling
• Query (replaces the old MySQL Query
• Administration (replaces the old MySQL Administrator)

Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

http://dev.mysql.com/downloads/workbench/

To get started quickly, please take a look at this short tutorial.

MySQL Workbench 5.2 RC Tutorial

Workbench Documentation can be found here.

http://dev.mysql.com/doc/workbench/en/index.html

In addition to the new Query/SQL Development and Administration modules, version 5.2 features improved stability and performance – especially in Windows, where OpenGL support has been enhanced and the UI was optimized to offer better responsiveness.
This release also includes improvements to the scripting capabilities of the SQL Editor. You can read more about it in

http://wb.mysql.com/workbench/doc/

For a detailed list of resolved issues, see the change log.

http://dev.mysql.com/doc/workbench/en/wb-change-history.html

If you need any additional info or help please get in touch with us.

Post in our forums, leave comments on our blog pages or if you want to talk to us directly you can visit us on our IRC channel #workbench on irc.freenode.net.

- The MySQL Workbench Team

Recently our development efforts were focused on dbForge for SQL Server product line. We’ve made five major releases of SQL Server database tools in last 18 months. Besides, we’ve made two major releases of MySQL database tools in this period. Our Oracle database tools product line, once actively developed, was frozen for almost three years. Sure we made maintenance releases, but no new features and tools. Our Oracle tools even were not re-branded to dbForge for Oracle. But now we decided to breeze the new life into Oracle tools development.

The first tool in the dbForge for Oracle product line will be Data Compare. For the first release we decided to make a free tool with basic functionality:

• comparison and synchronization of tables only (views are not supported)
• table and column mapping (by name)
• type conversion is not supported (column types must match)
• only simple types will be supported

Tool intended to help accomplishing simple database synchronization tasks and we plan to keep it free while adding new features to the commercial version.

Release is scheduled at the first decade of August 2010.

After gaining some experience in SQL Server data compare tools development we decided to release

Mikeal Rogers wrote a blog post on MongoDB performance and durability. In one of the sections, he writes about the request/response model, and makes the following statement:

MongoDB, by default, doesn’t actually have a response for writes.

In response, one of 10gen employees (the company behind MongoDB) made the following comment on Hacker News:

We did this to make MongoDB look good in stupid benchmarks.

The benchmark in question shows a single graph, which demonstrates that MongoDB is 27 times faster than CouchDB on inserting one million rows. At the first glance, the benchmark immediately looks silly if you’ve ever done serious benchmarking before. CouchDB people are smart, inserting such a small number of elements is a relatively simple feature, and it’s almost certain that either they would have fixed something that simple or they had a very good reason not to (in which case the benchmark is likely measuring apples and oranges).

Let’s do some back of the envelope math. Roundtrip latency on a commodity network for a small packet can range from 0.2ms to 0.8ms. A single rotational drive can do 15000RPM / 60sec = 250 operations per second (resulting in close to 5ms latency in practice), and a single Intel X25-m SSD drive can do about 7000 write operations per second (resulting in close to 0.15ms latency).

The benchmark demonstrates that CouchDB takes an average of 0.5ms per document to insert one million documents, while MongoDB does the same in 0.01ms. Clearly the rotational drives are too slow to play a part in the measurement, and the SSD drives are probably too fast to matter for CouchDB and too slow to matter for MongoDB. However, CouchDB appears to be awfully close to commonly encountered network latencies, while MongoDB inserts each document 50 times faster than commodity network latency.

At first observation, it appears likely that the CouchDB client library is configured to wait for the socket to receive a response from the database server before sending the next insert, while the MongoDB client is configured to continue sending insert requests without waiting for a response. If this is true, the benchmark compares apples and oranges and tells you absolutely nothing about which database engine is actually faster at inserting elements. It doesn’t measure how fast each engine handles insertion when the dataset fits into memory, when the dataset spills onto disk, or when there are multiple concurrent clients (which is a whole different can of worms). It doesn’t even begin to address the more subtle issues of whether the potential bottlenecks for each database might reside in the virtual memory configuration, or the file system, or the operating system I/O scheduler, or some other part of the stack, because each database uses each one of these components slightly differently. What the benchmark likely measures is something that is never mentioned – the latency of the network stack for CouchDB, and something entirely unrelated for MongoDB.

Unfortunately most benchmarks published online have similar crucial flaws in the methodology, and since many people make decisions based on this information, software vendors are forced to modify the default configuration of their products to look good on these benchmarks. There is no easy solution – performing proper benchmarks is very error-prone, time consuming work. It’s good to be very skeptical about benchmarks that show a large performance difference but don’t carefully discuss the methodology and potential pitfalls. As Brad Pitt’s character says at the end of Inglourious Basterds – “Long story short, we hear a story too good to be true, it ain’t”.

Interested in working at RethinkDB? We’re hiring – please see our jobs page for more details.