Archive for the ‘workbench’ Category

Webinar: Designing MySQL Databases (Italian) — Nov, 25@10am CET

Ноябрь 23rd, 2010
We already have more that 500 registrants for this MySQL web seminar. Join us and the crowd to learn the design dos and don'ts for MySQL. We will show you how to design, forward and reverse engineer databases including discussions on datatypes, indexes, and foreign keys for various application scenarios.

In this technical presentation, we will cover:
  • MySQL design basics
    • Data Modeling Basics
      • Physical and Logical Models
      • "Dos" and "Don'ts"
    • How to design MySQL for your specific application
      • Datatypes
      • Indexes
      • Foreign keys
  • MySQL Workbench
    • Design
      • Reverse Engineering
      • Design
      • Deploy (Forward Engineer)
      • Maintain (Synchronize)
    • Develop
      • SQL Coding

Whether you are developing commercial applications, Web-based applications, or in-house applications, and whether you are a novice or more advanced, you will benefit from this presentation.

When
Thursday, November 25th, 2010 at 10am CET


How

To register for this free web seminar please click here.
Related articles
Enhanced by Zemanta



PlanetMySQL Voting: Vote UP / Vote DOWN

How MySQL Workbench breaks itself

Ноябрь 21st, 2010
Once upon a time, there was a policy in MySQL not to add new features after the beta stage.
To my surprise, MySQL Workbench 5.2.30 introduces a new feature, the query formatter. I gave it a try. The results are not extremely encouraging. Granted, it's a plugin and not a feature in the core application, but nonetheless one would expect something more stable in a GA release, especially since the plugin features are displayed in the main menu, and unless you have read the announcement, you couldn't easily tell the core from the plugins.
This is what I have got in just a few minutes:

Bug #58356: beautify function fails on CREATE TABLE
Bug #58357: beutify function erases statement on CREATE INDEX
Bug #58358: query formatter fails on selected query
Bug #58359: query formatter indentation fails on partially selected query
Bug #58360 query formatter converts non-keywords to uppercase
Bug #58361 Query formatter mangles query when CASE operator is used

MySQL Workbench is a great product. I would like it to be more solid. New features, even as a plugin, should be more carefully released that this one.

PlanetMySQL Voting: Vote UP / Vote DOWN

Workbench called me a dummy!

Сентябрь 2nd, 2010

Seriously, it did.  Sorta.

I use Workbench for my daily work, and it’s a great tool.  If you haven’t tried the 5.2 release yet, you should.  While performing some maintenance, I happened to issue a DELETE statement against a table which had no indexes (it was 10 rows), and Workbench complained:

Error Code: 1175
You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column

It turns out this is a new feature in 5.2.26 (and is still there in 5.2.27) – Workbench now uses the equivalent of –safe-updates mode for the mysql command-line client (also known as the –i-am-a-dummy option – seriously).  This wasn’t exactly convenient for me, especially since the DELETE was part of a larger script which I then had to revise and step through manually after it failed, but there’s an easy way to change this behavior.  If you’re like me, you might consider disabling this:

  • Go to Edit -> Preferences
  • Select the SQL Editor tab
  • Uncheck “Forbid UPDATE and DELETE statements without a WHERE clause (safe updates)”

Despite the text, the –safe-updates mode affects more than UPDATE and DELETE statements without WHERE clauses – it requires such statements to explicitly use indexes.

I’m changing this behavior on my installation before I run into other problems.

I’m no dummy.  :)


PlanetMySQL Voting: Vote UP / Vote DOWN

Sometimes, even a command line guy likes a GUI

Май 14th, 2010
As everyone knows, I am a command line guy. I am very much comfortable with the shell prompt and the command line SQL client. I do most of my work that way, and I am very much productive.
However, there comes a time when even for a command line enthusiast a GUI can be helpful.
Here comes the latest MySQL Workbench 5.2.
There are two areas where I feel that WB can give me a hand:
The first is when looking at tables that contain BLOB columns. Sure I can deal with them at the command line, but this editor makes my life easier.

When a column contains a BLOB, you can open the field viewer.

At first glance, this is nothing more than what the command line could provide. I could get output in hexadecimal format quite easily in any client. But, looking more closely, there is a tab labeled "image" that is not as easy to come by at the command line prompt.

And there is Mike Hillyer, the main author of the Sakila database, who has stored his own image in the staff table for future generations. If you stick to the command line, you may easily miss this piece of self advertising.

The second area where I like having MySQL Workbench is when I need to change my configuration file with less than common options. Since no human (apart from Sheeri, perhaps) can remember all the options, I usually need to search the manual.

In WB, instead, I can edit the options file with the GUI, without need of remembering the exact names and spelling of the items I need.
Now, if I couple the above issues with the notion that MySQL Workbench is A Useful Tool to Centrally Manage Many MySQL Instances, I think that every command line enthusiast should give this tool a try.
Lastly, I should mention that Workbench 5.2 is becoming quite popular, as the downloads map shows.

PlanetMySQL Voting: Vote UP / Vote DOWN

North Texas 1st meeting of the year — Workbench & Cookies

Январь 2nd, 2010
Happy New Year! Monday night is the first meeting of the North Texas MySQL Users Group for 2010! And the topic for discussion will be MySQL Workbench.

Workbench is a tool for visual database design, schema documentation, change management, and is replacing the old MySQL GUI tools. If you have not tried the latest releases, you will be for a pleasant surprise.

NorthTexasMySQL.org meets at 7:00PM sharp at the Sun Offices, Suite 700, 16000 Dallas Tollway, Dallas TX. We welcome all who want to know more about MySQL, databases, or Open Source. Admission is free and I will bring cookies!

PlanetMySQL Voting: Vote UP / Vote DOWN

SSH Tunneling in Workbench 5.2.6 Alpha

Октябрь 23rd, 2009
Given the announcement earlier this week of an updated release of the actively developed MySQL Workbench 5.2, I thought I'd give it a quick look...

Install on Windows went without a hitch.

One thing I noticed, which I don't remember being previously available in MySQL GUI tools, is the ability to connect to a remote MySQL server via SSH tunneling.

Below is a screen shot:



Well done! A small, but significant addition for folks that require SSH to connect to their systems.

I did notice that the design in Workbench involves selecting "Standard TCP/IP over SSH" from the drop down and then providing credentials in a more "form" oriented layout. An "SSH" tab like we see in Navicat or SQLyog might be more familiar for some folks. (Also, a minor note, no "browse" button next to the "Path to SSH key file" option.)

I know that 5.2 is still in active development, but the functionality in regards to SSH looks good to go...with maybe just a few tweaks to the connections dialog :)

PlanetMySQL Voting: Vote UP / Vote DOWN

MySQL Workbench: Enabling Python in the GRT shell

Октябрь 8th, 2009

Yesterday, 7 Oct 2009, MySQL Workbench 5.2.4-alpha was released. What interests me in particular is that Workbench 5.2 brings support for writing plugins using Python. Before it was only possible using LUA.

Workbench comes with GRT (Generic RunTime) shell which allows you to access objects at runtime. It's pretty neat, but how you enable it to use Python? Here is how:

  1. Open the Workbench Preferences dialog
  2. In the General section, set Interactive GRT Shell Language to Python.
  3. Restart Workbench
  4. Go to View > Advanced and choose CRT Shell.

It's a bit of a chore writing in that shell as you can't copy/paste (at least not in MacOS, workaround is to drag!). Here are a few commands you can do there (or check on the Workbench team blog). Make sure you have at least one Model open, and one table defined.


>>> import grt
>>> model = grt.root.wb.doc.physicalModels[0]
>>> for tab in model.catalog.schemata[0].tables:
... print "Table: `%s`" % (tab.name)
...
Table: `t1`

Using the GRT shell it makes it possible to test first some lines of code. I do personally like it, although the shell feels still a bit buggy, but usable.


PlanetMySQL Voting: Vote UP / Vote DOWN

MySQL Workbench Italian Webinar

Сентябрь 15th, 2009
MySQL_WB.jpg

On Thursday, July 17 there will be a web based seminar on MySQL Workbench.

Seminar will be in Italian and anyone who is interested is invited to join us. You can find details here.

If you are a database architect and you usually work with data models this tool is going to make your life easier and you will learn some interesting features. In the meantime, to better understand the product, take have a look at http://dev.mysql.com/workbench/, where you can download a copy of the community version, read blogs, contribute, discuss and learn.

Happy data-modeling!

PlanetMySQL Voting: Vote UP / Vote DOWN

Workbench 5.2 Alpha

Июль 30th, 2009

In case you have not already noticed, Workbench 5.2 alpha / preview release of MySQL's premier development and design tool, has been announced.

For an independent preview, you can also see here