You will no longer receive e-mail notifications from this forum.
Log-In to post
I'm seeing a table schema popup (tooltip style) when I hover my mouse pointer over a table name in a query in the editor. Is there an option to turn this off? I find it pretty annoying, I get that info from code completion or I I'll get it from the Object Explorer. The main thing is that while it's there it covers up everything under it and I cannot use my mouse to select code. So can I turn it off? If not, then consider this a feature request (to make it optional), or a feature remove request (drop it altogether).
Hi.. not sure which forum this should go into. But here is the link to the other post:
In the current betas I have noticed that when I change the tab in the Object Explorer (for example I change from the Tables tab to the Procedures tab) the database sometimes switches to a different database. It seems that the database is set for each tab and as you change tabs the database switches to the one last used with a particular tab. I realize this may be somewhat of a personal preference, but I think that the database should never switch automatically, once I select set the database it should stay set until I change it otherwise it bounces around all the time as I change the tabs - surely if I'm looking at Tables in a particular database, I most likely want to look at Procedures in the same database?
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!
I get the following exception about once a day, it happens when I'm typing SQL in the editor and the code completion popup appears:
System.NullReferenceExceptionObject reference not set to an instance of an object.Stack Trace: at Quest.Toad.MySQL.Trl.ParameterListTrl.get_Data() at Quest.Toad.MySQL.Trl.ParameterListTrl.GetTrls() at Quest.Toad.CodeInsight.MethodInsightItem.FetchData(Object unused)
In the current beta (184.108.40.2061 or 220.127.116.111 depending on where you look) I am getting an exception thrown whenever I am looking at a procedure in the Viewer.
With the Viewer open, click the connection selector in the bottom right corner and select a different connection (that has the exact same databases - for example a local server connection and a development server connection) and this exception is shown every time:
Object reference not set to an instance of an object.Stack Trace: at #CLe.#zMe.#q5e(Int32 #tRe, Int32 #fd) at ActiproSoftware.SyntaxEditor.DisplayLineCollection.#mmc(Int32 #8Ve) at ActiproSoftware.SyntaxEditor.EditorView.LocationToPosition(Point #bVe, LocationToPositionAlgorithm #Nyf, Boolean #Oyf) at ActiproSoftware.SyntaxEditor.EditorView.LocationToPosition(Point location, LocationToPositionAlgorithm algorithm) at ActiproSoftware.SyntaxEditor.SyntaxEditorHitTestResult..ctor(SyntaxEditorHitTestTarget target, EditorView view, IUIElement element, Point point) at ActiproSoftware.SyntaxEditor.SyntaxEditor.HitTest(Point point) at ActiproSoftware.SyntaxEditor.EditorView.OnMouseLeave(MouseEventArgs e) at ActiproSoftware.WinUICore.UIElement.#hxe(MouseEventArgs #yhb) at ActiproSoftware.WinUICore.UIControl.#Xwe(IUIElement #irb, MouseEventArgs #yhb) at ActiproSoftware.WinUICore.UIControl.OnMouseLeave(EventArgs e) at System.Windows.Forms.Control.WmDestroy(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at ActiproSoftware.SyntaxEditor.SyntaxEditor.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
If I close the exception window everything keeps working normally.
Just upgraded to Windows 10 on a new work machine and Toad for Mysql is providing the following error during start up:
BadImageFormatExceptionBad IL range.
Stack Trace: at System.Windows.Forms.FileDialogCustomPlacesCollection..ctor() at System.Windows.Forms.FileDialog..ctor() at System.Windows.Forms.SaveFileDialog..ctor() at Quest.Toad.Gui.MainForm.InitializeComponent() at Quest.Toad.Gui.MainForm..ctor() at Quest.Toad.StartupForm.MainAppicationEntryPoint(String args) at Quest.Toad.ToadProcessEntryPoint.Main(String args)
The application fails and has to be closed. I have tried versions 7.5 and 7.7, as well as running in Windows 7 compatibility mode.
It seems (I don't know because no release notes are ever given for beta releases) that in the current beta (18.104.22.168) the Editor has been changed to show syntax errors in the Output pane while typing - I'd like to ask that this be changed back to only do this when saving the file or at least not until I run the query. Until a query is finished it will naturally be one big syntax error and I don't need a flashing distraction at the bottom of my screen telling me on every keystroke that I'm not done yet. Worse still is the fact that in order to show me the error that isn't really an error, the Output pane has to switch from the grid that was showing my last results so now I can't see what I wanted to see while typing my current query.
You can change the DateTime displayed in Options -> Environment -> Grid -> Data Type Formatting, DateTime tab and this will change ALL datetypes to the chosen format. Under the Custom TAB, I've added specific datetime datatypes such as TIME, DATE, TIMESTAMP and DATETIME (see attachment) to overwrite the all-inclusive value, but it doesn't change the grid data at all.
If you start a query that is taking a long time, and hit the Cancel button, the UI says it's cancelled but if you run 'show processlist' you will still see it running.
And.. if you start a long query and then go and kill that session from somewhere else, Toad will still continue sitting there waiting for it.
The Toad 7.7 beta expired on 11/5, can we please get an update.
I'm trying to use the comparison wizard. However I get the error Keyword not supported 'btkkw;pooling' when I try to select the database for a remote server. In this instance it is a Hostgator server. There seem to be no problems with the localhost server. Previously there haven't been any problems. Any suggestions on how to resolve this?