Toad® for MySQL
Beta Version 5.0.0
Beta Release Notes
February 26, 2010
Toad for MySQL is a database development and administration solution that provides productivity features for rapidly creating and executing queries, automating database object management, developing SQL code, and instant access to MySQL expertise.
Developers and administrators have access to a community of users, peers, and experts to help solve development and administration issues and assist in developing applications and feedback for improving Quests products.
All of this comes with the backing of Quest Software, a healthy and growing corporate
entity that can provide the necessary training, support, and superior customer service
demanded by IT management.
You can now view RSS and Twitter feeds,
including Toad Community postings from within Toad using the new Collaboration
window. You can access this window from View | Collaboration. Once open,
you can click any entry to open the related content.
An
icon
indicates an RSS feed and an
icon
indicates a Twitter entry.

When you open the Collaboration window, it polls all RSS and Twitter feeds that you have defined in the Collaboration options page (Tools | Options | Environment | Collaboration). The first time you open the Collaboration window, the options page automatically displays.

In the Collaboration options page, you can also define your Twitter account details and a Twitter search to follow in Toad. The search defaults to a specific search depending on which product you use. By default, any posts in Toad are posted to this specific search. You can also clear the Only Search checkbox to display all your twitter posts.
In the Collaboration window, you can click
at the top
of the window to compose a new entry. You can select the drop-down arrow beside
the icon to select which feed you want to post to.
To post to Twitter, use the entry field at the bottom of the window. When using Twitter, if you click an item in the list, an appropriate reply entry is entered in the field. If the post contains a link, that link is opened in the Web Browser as well. To post an update, press ENTER or click the lower-right Twitter icon. If you click the camera icon to the right of the twitter icon, you can toggle whether you want to include a screen shot of Toad with your post (After posting, this option always reverts back to false).

You can now execute an export template against a different connection than the one saved with it. For example, this allows you to use the same export template against your test, development, and production databases. To execute the template against a different connection, make sure you are connected to, and the new database has focus in the Connection Manager when you execute the template.

You can now execute an import template against a different connection than the one saved with it. For example, this allows you to use the same import template against your test, development, and production databases. To execute the template against a different connection, make sure you are connected to, and the new database has focus in the Connection Manager when you execute the template.
The following improvements have been made to code completion:
You can now multi-select some objects in the code
completion list. If an object can be multi-selected, a check box displays
next to it. You can then select the checkbox or press CTRL+SPACE to select
the object.

For objects such as schemas and databases, you can now expand these objects to see other items that are associated with them from code completion. You can view these items by clicking the + sign or by pressing CTRL+RIGHT.
You can use the new toolbar at the bottom of the code
completion list to change the following code completion options (in order):
Apply filter to editor, Include system objects, Merge secondary items.

You can use the resize grip in the lower-right corner to resize the code completion drop-down list. The new size is also remembered between Toad sessions.
You can now quickly navigate between items that match what you have written in the Editor by pressing the keyboard shortcuts CTRL+UP or CTRL+DOWN. This is especially useful if you are searching for matches in different types and have set the sort option to sort by type.
Code items no longer fetch their parameter information when the list of code completion items is generated. That information is now fetched when it is needed, which leads to greatly improved performance. We also generate more detailed comments on code completion for these, including data type, direction, and parameter comments.

We no longer include all the prefixing elements of
objects in the code completion drop-down list, which leaves more space for
the relevant part of the name.

When selecting
several items in a Where clause, they can now be combined correctly into a
code snippet.

The code completion drop-down list now disappears if you click anywhere outside the drop-down control. Also, if you move the caret in the editor outside of where it could form a valid drop-down entry it also disappears (for example, if you move to the left of the insertion point).
As you can see in the previous screenshots, the expand button and multi-select checkboxes only display when they are needed.

The parameter hint contains a description of the parameters with the parameter currently being edited displaying in bold. Below that is a description of the code if it exists, and on the last line a description of the currently focused parameter displays.
The debugger trace functionality adds the ability of any Toad debugger to generate a trace on a piece of code executed through a debugger, which can then later be replayed to investigate what actually happened during the execution. One additional feature of replaying the trace is that you can step both backwards and forwards in the debugger to evaluate the execution.
You enable debug trace collection by selecting the
Collect debug trace checkbox in the Debugger Start Parameters window that
displays when starting a debug session. You can also open this window by
clicking
on the Debugger toolbar.

Note: This flag is cleared after every execution (You probably don’t want to collect execution traces on every execution).
You can also enable and disable trace collection while executing using a new toggle on the Debugger toolbar.
![]()
When a debug trace has been created, a window displays that lets you browse through, delete, and replay debug traces. You can also open this window by selecting Debug | Windows | Debug Traces from the menu.

Each item in the list represents saved debug traces and you will only see the
traces that were created for the current connection. When you hover over an item
in the list, the full name of the piece of code and the value of any specified
parameters when you executed it display. To replay a trace, double-click it in
the list or click
.
You can also generate a coverage report from the trace by clicking
.

The debug trace collects the following:
· Local parameters and arguments. Global variables are not collected by default, but can be enabled in the options.
· Step information and callstacks.
· Scripts of all involved code. This means that when you replay a trace you will see the script in the editor as it looked when the trace was created regardless of whether the object has been changed in the database.
The debug trace does not collect the following:
· Anything returned to the script result or output.
· The final return value from a function.
When you are executing a trace, the following additional toolbar buttons display to let you step over backwards, step into backwards and step out of backwards.
![]()
In addition, debug trace options are available in Tools | Options | Debugger | General.

The first option determines whether the trace should record every line executed while debugging or the lines where you break or step over. By default all lines are executed.
The second option determines whether global variables are recorded in the trace. By default, this is not recorded for performance reasons.
|
Feature |
Resolved Issue |
Change Request |
|
Feature |
Known Issue |
Change Request |
|
Schema Compare |
Choosing the menu item causes Toad to throw an error |
CR#54,178 |
|
Format code |
Toad inserts a space between a function and the left parentesis. Formated code does not run. |
CR#54,845 |
|
Opening Index from Database Explorer |
Toad throws an exception when user tries to open an index by double-clicking on it from the Database Explorer's "Index" tab. |
|
The following is a list of third party issues known to exist at the time of Toad for MySQL release.
|
Feature |
Known Issue |
Change Request |
|
Data Grid |
Currently, Korean characters are not supported. |
CR#41,612 |
|
Export Data |
In order to export to an Office 2003 or 2007 Excel instance, the Office Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from one of the following locations: 2003 PIAs 2007 PIAs |
CR#138239 |
|
Output |
Currently, Korean characters are not supported. |
CR#41,612 |
|
Database Browser |
NotSupportedException when viewing data from a table that has a Geometry data type column |
CR#42,393 |
Before installing Toad for MySQL, ensure your client system meets the following minimum hardware and software requirements:
| Platform |
1 GHz |
| Memory |
512 MB of RAM minimum, 1 GB recommended
|
| Hard Disk Space |
|
| Operating System |
Windows Server 2003 (32-bit or 64-bit) Windows XP Professional (32-bit or 64-bit) Windows Vista Windows Server 2008 Windows 7
|
| Additional Software |
.NET Framework
Web Browser
|
| Supported Databases |
MySQL 5.0 MySQL 5.1 |
The following user privileges are required for installing and running Toad for MySQL:
From the Windows Start menu, select Settings | Control Panel.
- Double-click Administrative Tools.
- Double-click Microsoft .NET Framework 2.0 Configuration.
- Click + to expand My Computer, and then select the Runtime Security Policy node. A list of tasks for the node display in the right panel.
- Click Evaluate Assembly from the list of tasks in the right panel. An Evaluate an Assembly window displays.
- Browse to the location of Toad.exe in the File field.
- Click Next to view permissions for Toad.exe.
- Set the permission to Unrestricted.
This section contains information about installing and operating this product in
non-English configurations, such as those needed by customers outside of North America.
This section does not replace the materials about supported platforms and configurations
found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release,
all product components should be configured to use the same or compatible character
encodings and should be installed to use the same locale and regional options. This
release is targeted to support operations in the following regions: North America,
Western Europe and Latin America, Far-East Asia, Japan.
© 2010 Quest Software, Inc. ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc.
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
|
Quest Software World Headquarters
LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.