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

This is for users who don't like HeidiSQL to store usernames and passwords somewhere:

Activating this new checkbox will ask you for username and password on demand, each time you connect to this session. Both previously stored username and password are taken as the default credentials when prompting.
PlanetMySQL Voting: Vote UP / Vote DOWN

Dear MySQL Users,

We’re pleased to announce the release of MySQL Workbench 5.2.25  This release is GA (Generally Available). We hope you will make MySQL Workbench your preferred tool for Design, Development, and Administration of your MySQL database applications.

Special thanks go to all the great MySQL Beta Testers that provided valuable ideas, insights, and bug reports to the Workbench Team. Your beta feedback truly helped us improve the product.

MySQL Workbench 5.2 GA provides:
• 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.

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

MySQL Workbench 5.2 GA Tutorial

Workbench Documentation can be found here.

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.

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

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

PlanetMySQL Voting: Vote UP / Vote DOWN

Dear MySQL Users,

We’re happy to announce the 3rd Release Candidate (RC) of MySQL Workbench.
Version 5.2.24 includes fixes for more than 70 issues.

MySQL Workbench 5.2 RC provides:

• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)
if you are a current user of MySQL Query Browser or MySQL Administrator, we look forward to your feedback on all the new capabilities we are delivering in a single unified MySQL Workbench
As always, you will find binaries for the various platforms on our download pages.

Please get your copy from our Download

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

Please be aware that this release is still a in-development version – so please don’t use it on your production servers! Also note, MySQL Workbench files saved with version 5.2 cannot be opened with previous versions of our program.

The files for several platforms have been pushed to our main server and should be available on our mirrors.
Blog postings and general information – including build instructions for Linux – can be found on our Workbench Developer Central site.

Workbench Developer Central

http://wb.mysql.com

Workbench Documentation and details on changes between releases can be found on these pages

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

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.

Product Hint: All the quick keys are shown in the product, so always remember to look at mouse over icons or in the menu listings.

Thanks again to all those testing MySQL Workbench and providing insightful ideas, enhancement, and issues as well.

- The MySQL Workbench Team

PlanetMySQL Voting: Vote UP / Vote DOWN

Users of the latest HeidiSQL build file will find a new option when rightclicking a data grid: "Copy selected rows as LaTeX table". Same applies to the "Export grid data ..." which is capable of storing rows in LaTeX format to a file.

Thanks to brampton for the patch!

Now there are 5 different text formats supported in grid exports: CSV, HTML, XML, SQL and LaTeX. Probably you know some more reasonable file formats to support?
PlanetMySQL Voting: Vote UP / Vote DOWN

From time to time dialogs need some usability refactoring. So happened with the good old Copy table dialog in HeidiSQL. New features:
- Select specific indexes or foreign keys to be created in the new table
- An editor for a WHERE clause, for cases in which you only need a subset of the original row data in the target table
- A menu for recently used WHERE clauses, so you don't need to keep them all in mind
- Prompts for overwriting if the new table exists



Thanks to Daniel for ideas and feature request number 2,000.
PlanetMySQL Voting: Vote UP / Vote DOWN

Users of HeidiSQL 3.x may have missed this feature since grid and BLOB editing was rewritten for v4: A preview area for images. Now it's even more powerful than before: it detects and loads various kinds of images (JPG, PNG, GIF, BMP, PSD, TIF and more). Also, the new preview area does not take valuable space when you're in some grid, as it's placed below the database tree:



PlanetMySQL Voting: Vote UP / Vote DOWN

After having updated to the latest build via Help > "Check for updates" you will be able to see more than only the result of the last SELECT query in any "Query" tab. By default, HeidiSQL displays up to 10 result sets in subtabs. In case you want more just go to

Tools > Preferences > Data

and increase this value in Maximum number of query results. Different than before, these are the first result sets from your SQL code.



Please note that HeidiSQL still does not separate multiple results from a stored procedure. Will be the next thing to implement soon.

Also a minor new feature is the hint on the lower statusbar when hovering over the MySQL version. You will see various connection, server and client related details here.


PlanetMySQL Voting: Vote UP / Vote DOWN

In the last few months we’ve got couple of bugs with the PBXT read/write locking code. One of the problems was directly in the lock/grant algorithm. It was strange to find such kind of error after quite long time of various testing and real-life usage. From the point of view of QA it was clear that manual code review was not efficient in this case.

Given all this I decided to try formal verification of the code. The specifics of the PBXT locking code is that it’s relatively small (about 100 LOC) but quite complex. The algorithm itself is not that trivial but the major source of complexity is concurrent execution of its parts. So if I had to manually create a finite state table for it then it would be essentially a cartesian product of states of all concurrent threads. In numbers that is if there is about 20-30 states per thread and there are 3 threads (empirically I estimated that threads beyond 3 don’t add more states) then I would get between 8000 and 27000 of states to check - quite a bit of work to do on a piece of paper (and a very good example of multithread complexity).

So I decided to try a verification tool. After some evaluation I picked SPIN. Verification with SPIN bascially consists of 2 steps: 1) build SPIN model 2) run verification and/or simulation.

I built 2 models - the buggy one and (presumably) fixed one. The buggy version triggered an assertion after a second of simulation (compare that to months of C code testing!) while the fixed one successfully passed both simulation and verfication.

Does this mean the code is bug-free? The answer is - the SPIN model is bug free. But given that it fairly close resembles the code chances are very high that the code is bug-free as well. Knowing this will save us some debugging time in future.

This was my first practical experience with formal verification. If you use formal verification in your work then please let me know which tools do you use, what kind of code do you check, general considerations, etc…

Thanks

PlanetMySQL Voting: Vote UP / Vote DOWN

Recently I rewrote the whole internal grid editing stuff to have bidirectional record sets. Means, editing grid data is no longer restricted to the Data tab. Any Query tab now allows you to edit your row data - at least if it's a simple query without joins and if it contains sufficient key columns. This was one of the most wanted features by users, described in issue #723.

As a side effect, query results are client-sortable now. When you click a column header, the grid itself is just sorted. This is surely not a replacement for having an ORDER BY clause in your query, but helps a lot to work quicker with simple grid results. Note that the Data tab works different here - the SELECT query is reposted with an adjusted ORDER BY clause. Only for the query tabs this is not possible as the query is totally user edited, no internal (and probably unsafe) SQL parsing is done.
PlanetMySQL Voting: Vote UP / Vote DOWN

It’s a busy time of year for Pythian. With many of our team tied up on client engagements, away at MySQL conference this week, and Collaborate 2010 next week, I’m pinch hitting as volunteer editor in helping to pull together this week’s edition of Log Buffer. Enjoy!

MySQL Conference 2010

Big news this week from MySQL Conference as Oracle’s Edward Screven elaborates on Oracle’s plans for MySQL in his opening keynote. Pythian’s Paul Vallee was interviewed by Network World’s John Brodkin, before the conference in anticipation of the session.

Ronald Bradford responds, writing about his disappointment with the keynote and then elaborates on being named an Oracle ACE Director.

Pythian’s Sheeri Cabral, recently recognized for her MySQL community contributions as Oracle’s first ACE Director for MySQL was in the middle of all the action. Sheeri outlines how Oracle can be MySQL’s friend-with-benefits in her community keynote. And then shares her thoughts on Drizzle with O’Reilly Media’s Tim O’Reilly. And on the keynote, Sheeri comments it was an ad to “come join us at OpenWorld”.

Rob Hamel gives running commentary on MySQL Conf Day 1 and Day 2.

Oracle

Thanks to my colleague Chen Shapira, here’s the latest in the Oracle World:

Catherine Devlin, the Python-Oracle Geek shared her idea on how non-profits can share their IT resources.

Miladin Modrakovic on the Oraclue blog demonstrated how to turn physical standby to a snapshot standby. It is easier than Chen thought.

Jonathan Lewis reminds the DBA community that UKOUG opened the call for papers for their famous conference. DBA’s – send your submissions, the deadline is August 2nd. Pythian will be submitting, maybe we’ll see you there. On a related note, if you’re reading from down under, the deadline for the AUSOUG call for papers, co-located this year with InSynch2010 is now May 15, 2010.

He also shows how Oracle uses the /*+ rule */ hint in some internal views – and everyone knows you should never do that.

Rob Zoeteweij at the OEM Grid Control blog announces the availability of OEM Grid Control 11.1 for Linux.

Tom Kyte blogs again! He has a new series about new things he learns every day. That’s a lot of learning from someone with 23 years of Oracle experience!

He also demonstrates the test process he uses to adapt his “Expert Oracle Architecture” book to the latest oracle versions. His test-and-verify process is a good example for all DBAs.

Pythian’s own Brad Hudson posts instructions on how to install TOra, the graphical Oracle client, on the latest Ubuntu release (Lucid Lynx).

And lastly, a post from Alex Gorbachev on the opening of Miracle OpenWorld 2010 in Denmark this week. Fingers crossed, he’ll then jet off to Vegas next week for Collaborate, presenting the “Worst Practices of IT Outsourcing” with Paul Vallee. Say hi if you’re in town.

SQL Server

From Michelle Gutzait, and Edwin Sarmiento, for updates on the SQL Server side of things, a new site launched containing all world-wide events for SQL Server

Buck Woody’s quote of the day is “Always Use Diplomacy”. Remember this, and then learn how to create and track your own license keys using PowerShell.

Adam Machanic hosts this week’s T-SQL Tuesday #005 on Technical Reporting.

Paul Randall writes about important things a DBA should consider and then follows that up with his A SQL Server DBA Myth A Day #15 (of 30) checkpoint only writes pages from committed transactions .

Please remember that we’re always looking for volunteer editors for Log Buffer. If you want to host the next edition send a note to Log Buffer coordinator and read up on our guidelines for publishing.

Have a great weekend.

PlanetMySQL Voting: Vote UP / Vote DOWN