When typing a query into MySQL Workbench, the autocomplete suggestion popup is so slow. After typing a couple letters of a column or table name, I have to pause for about a second or more for the suggestion box to popup.
Is there anyway to make the suggestion box appear immediately as I'm typing rather than wait for a pause?
This is on purpose to avoid that the popup comes up constantly while you are typing (the delay is 500ms atm, hard coded). However, by using the hot key you can always trigger code completion immediately (on OSX this is command + esc, otherwise control + space bar).
Yes, It works
If you have each schema open (dropped down) in the Navigator, the autocomplete will work.
Thanks
for more information refer to this link
MySQL bugs
Thanks
Related
I have logs to monitor.
If an error message appears in log, I want trigger to be activated - it works fine.
Now, I want trigger to stay activated until someone sees the error, and it can take from 1 minute to several days.
I cannot use "count()" and want to avoid sending an email or something like this. I've tried to use count(LARGE_VALUE) - now triggers stay long enough, but cannot be deactivated and using "unacknowledged only" filter does not help, since acknowledged triggers do not repeat if an error happens again.
Same functionality can be achieved by some external monitoring, but I want to avoid this if possible.
I've also seen this issue, but hope there still is a way to solve my problem, since it seems pretty common.
I am using PHPStorm 9.
I have installed PHPCS to sniff my code. It is properly configured, up and running.
I am working on a very old project, which was implemented in plain PHP, and not using any code standard.
As a result, every time I open any of those files, I get a message at the top of the screen saying that I have too many errors (code style errors).
I have a couple of problems with that.
First, I already know how bad the code is, so I don't need PHP Storm to tell me that all the time.
Second. That message appears and disappears every time I edit the code. As a result, the window editor is constantly moving up and down, which I find specially annoying.
Also, at the top of the screen it is showing me the breadcrumbs, to tell me where I am. I appreciate the help, but I don't actually need it.
So the question is, how can I configure the IDE to disable those two messages? (read arrow and orange arrow in the attached image).
Please notice that I don't want to disable PHPCS. I only want to turn off those annoying messages.
I was unable to find it out by myself because I don't even know how those messages are called. Certainly not 'popups', nor 'status bar'
Best regards
Nicolas
Answering my own questions, thanks to the help of the PHPStorm Support team, Vladimir Luchansky (perhaps you need to create an account to see the thread):
To disable breadcrumbs: Go to File->Settings->Editor->General->Appearance, and untick the option Show HTML Breadcrumbs. Then restart the IDE
To disable the PHPCS messages without disabling PHPCS itself: Well, that option is not available in PHPStorm 9. It will be available for a future release. According to Vladimir, a developer is working on it. In order to make this request to go up in the future request list, the request needs to get as much 'votes' as possible. So, if you are interested in this feature to be ready ASAP, please vote up here.
Best,
Nicolas
I don't believe there's any mechanism for suppressing those phpcs: Too many messages per file alerts. As an alternative solution, you could give this work-around a try:
Clone your current inspection profile via Preferences > Editor > Inspections. Name the new one "Strict (with phpcs)". Then, choose your old inspection profile from the Profile: dropdown box (thus, reverting your project's default inspection profile to your old one). Rename it to "Weak (without phpcs)" and disable phpcs for that particular profile by unchecking the PHP > PHP Code Sniffer validation option.
From this point forward, phpcs inspections (and related alerts, like the one you're concerned about) won't come into play as you're editing your files. However, whenever you do want to inspect one of your files using PHP Code Sniffer, you can do so easily via Code > Inspect Code > Inspection Profile > Strict (with phpcs)
Hope this helps!
The greatest strength of phpMyAdmin (IMHO) is that it seemed to strike the perfect balance between GUI comfort and raw coding of SQL.
I am currently on version 4.1.13, and recent versions have tended to try to introduce a few jQuery UI effects and AJAX.
Now I am having serious trouble with this scenario:
To edit an index, a UI dialog is called up. After save, all is well, but the problem is, the SQL statement(s) invoked is flashed for only a fraction of a second, then slideUped out of view.
If you're like me, you sometimes want to copy out this SQL code, to be run on another schema, or for whatever reason.
I thought I could find a setting to turn off some of these UI effects, but naah!
So, is there a way I can turn off the sliding away of the last used SQL? Even a hack would be okay for me right now.
Thank you.
Version 4.1.13 is outdated, please try the latest stable version.
I'm trying to extend the behaviour of ttk::combobox to make it behave like the Google search box in my browser - i.e. I'd like it to drop down automatically and limit the entries in the listbox to those which match the string that I've typed in so far. Ultimately, I'd like to select the part of the string that's been autocompleted so that the next character the user types will cause it to be deleted and re-start the matching process.
I found the page on the Tcler's wiki, but that appears to select the entry with the letter just typed, which isn't what I want. (Consider a user selecting from a list of US States. When they type A, I want the selection to be limited to Alabama, Alaska, Arizona and Arkansas; when they then type an L, the list should be limited to Alabama and Alaska. The code on the wiki would select Alabama when the user types A, then Louisiana when they type L.)
I tried defining a few bindings on the ttk::combobox, but gave that up - to be honest, I can't remember why - and have tried to extend the behaviour of a ttk::entry to cover it.
After borrowing liberally from ttk/combobox.tcl I've managed to post a listbox and to limit the entries in the listbox, but am having big problems now that I've added bindings to make the up and down arrows alter the selection. To be precise, the selected item is moved happily, but some of the time when the entry widget loses focus, the whole application hangs up and my tclsh soaks up all the CPU.
I'm developing using ActiveTcl 8.6 on both Windows and Linux and the code seems to behave the same on both platforms, although I haven't tried on Linux since I first saw it not hanging in Windows. I'd be very happy to share my code, but since the demo script runs to about 450 lines, I wouldn't read it myself if someone else posted that much.
Can anyone help by asking the right question to set off a lightbulb for me? The problem feels like a timing problem, but I've no idea where to start trying to track it down.
Many thanks.
Edit I've been racking my brain, and I think the reason I abandonned the attempt to extend ttk::combobx was because there were already a large number of bindings in place, and some did things that I didn't want. The current effort uses a validatecommand on the entry widget and Key-Up, Key-Down, FocusIn and FocusOut bindings.
Current code is on pastebin here.
Well, that was embarrassing!
I took another look at the code on the wiki and discovered that it did the thing I most wanted. It doesn't post the listbox, but it does autocomplete, and if you attempt to navigate the (unposted) listbox, by pressing Key-Up or Key-Down, it starts off with the appropriate item highlighted.
That's quite enough for what I need; if I decide I really must have the listbox posted, I can see about that at the time. (Given my bad experience trying to roll my own, however, I suspect that I'll just live with this.)
Many thanks for the forebearance and suggestions.
I'm using php storm on a mac.
To move a selection up or down (move statement up/down), the shortcut is cmd + up/down.
If you press this shortcut multiple times that's fine.
But sometimes you just want to hold the shortcut down and see the selection going up or down.
(It saves you from typing the shorcut multiple times).
The problem I founded is that in this case where you hold the shortcut down : there is too much time
between the moment where you push the shortcut and the moment where php storm understood that you want a "holding shortcut" operation.
Is there a setting to customize this time please ?
I didn't find it.