You will no longer receive e-mail notifications from this forum.
Log-In to post
These people make Toad for MySQL Beta Program great and have the most points for this month!
In 220.127.116.111, I am unable to pin any of the result tabs (e.g. Set 1, Set 2, etc.). Under some circumstances, I can see a ghosted pin (only on one of the tabs), but the tabs cannot be pinned. This was functional under .528
A new beta for Toad for MySQL has been posted and is now available for immediate download. Just head over to the download section and get it right now!
This build also reintroduce the ability to connect to databases that use old style 4.1 version passwords again.
It appears that V18.104.22.1688 has expired and I do not see any versions later than .528.
Is there a timeframe for the next Beta update?
In the current beta (22.214.171.1241) line numbers are no longer displayed in the Editor. I have line numbers turned on in Options and I used to see them in the previous betas.
Toad for MySQL v126.96.36.1998 Beta is now available
Toad for MySQL v188.8.131.521 Beta is now available
My editors’ execute script buttons randomly stop working. I click the icon or arrow, but nothing happens.
I have to restart Toad every time.
I have 184.108.40.2062, and it did this in at least the last beta, too.
Toad for MySQL v220.127.116.112 Beta is now available
Toad for MySQL v18.104.22.1682 Beta is now available
Toad for MySQL v22.214.171.1242 Beta is now available
I am using the new 126.96.36.1991 beta and it has been really stable for about 4 days, but today I'm getting exceptions. Three exceptions windows open on top of each other when I open a new Editor, the messages in the windows are:
This one shows in three separate Error Message windows:
System.NullReferenceExceptionObject reference not set to an instance of an object.Stack Trace: at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)
This one shows in its own Error Message window:
System.ArgumentOutOfRangeExceptionIndex was out of range. Must be non-negative and less than the size of the collection.Parameter name: indexStack Trace: at System.Collections.ArrayList.get_Item(Int32 index) at DevExpress.XtraBars.BarItemLinkReadOnlyCollection.get_Item(Int32 index) at Quest.Toad.Editor.EditorForm.ExecuteSmartIdle(BarItem barItem)
After the exception occurs the Execute script button on the toolbar is grayed out and I cannot use it, but pressing F5 or selecting Execute SQL on the Editor both still work and do execute the SQL.
The first time it happened, I had been using Toad for about 4 days ever since I first installed the new beta on 10/24, I then closed Toad and started it again and it worked normally for a few minutes and then the exception occurred again.
Toad for MySQL v188.8.131.522 Beta is now available
If I have the Triggers tab in the Object Explorer selected and I execute SQL to drop all triggers, then I get the following exception in Toad 184.108.40.2061:
System.ArgumentOutOfRangeExceptionIndex was out of range. Must be non-negative and less than the size of the collection.Parameter name: indexStack Trace: at System.ThrowHelper.ThrowArgumentOutOfRangeException() at Quest.FastData.FastTable.RowCollection.GetFastRow(FastTable fastTable, Int32 index) at Quest.FastData.FastTable.System.Collections.IList.get_Item(Int32 index) at Quest.FastData.FastRowCollection.get_Item(Int32 index) at Quest.Toad.MySQL.Trl.TriggerTrl.get_Source() at Quest.Toad.MySQL.Trl.TriggerTrl.SourceTrl.get_Source() at Quest.Toad.MySQL.Dov.ScriptViewControl.Source(ITrl trl) at Quest.Toad.MySQL.Dov.ScriptViewControl.DataUpdated(Object sender, EventArgs args) at Quest.Toad.Cache.LiveCache.UpdatedProxy(Object sender, EventHandler handlers)
The first beta for Toad for MySQL 7.5 has been posted and is now available for immediate download. Just head over to the download section and get it right now!
I downloaded the beta version to see if connections via SSH (to something like AWS) were better supported in the product. I didn't dig around in the details, but could not find that it was. Am I missing something?
To make it confused, just cause a connection to DB to be interrupted and then try to use all functionality. The weird thing is that Editor windows likely will work, but things like DB explorer or Session monitor will fail and totally hang and mess up Toad requiring you to kill the whole app.
The error window constantly pops up, locking the entire application.
This is with ver 220.127.116.1144 but in general it does not matter.. Toad has been plagued with this for years. Starting with Ver 7 is has been MUCH BETTER! But still there is some fundamental flaw in error handling and consistency across the application.
I will try the latest beta update.
For a long time I thought setting the WAIT_TIMEOUT and INTERACTIVE_TIMEOUT values did not work in MySQL. I was really shocked to find that actually it worked fine, but it was TOAD that would always display the wrong values!!! (seen in DB explorer)
No matter what the setting was set to, for both of those it would always show a value of 2000000.
Even if inside an Editor window I run this:
show global variables like '%timeout%'
I get the CORRECT value.
This blew me away. :)
Every time there is an update, there is always a mystery as to what was changed.
And the Install habitually continues to show Release notes for some PREVIOUS versions.