My DataGrip run/debug configuration wrong and can`t run SQL console script - mysql

I am learning mySQL and practice basic syntax using DataGrip. Unkownly, I can`t run my console script.
For example,I enter SELECT * FROM table in the console window,and click the green button 'run', But it can`t run as ususal.

I assume you go to the context menu and press 'Run console_1' or used the green arrow on the upper toolbar. This actually created a run configuration for the whole script. And it is noе what you needed. To run just a single query:
Use the green arrow button on the console toolbar.
Or the shortcut: Cmd+Enter
Or in the context menu choose Execute

Related

How do I prevent a Slate query from running automatically when the Slate document loads?

I have a query and I only want it to run when I click on a button, but not before.
How do I control this?
You can set queries to run manually from the query editor.
Press the button next to Run with the down arrow to get the query options, and check the box next to "Run Manually".
Note: If you set a query to run manually, it will not run on document load or when its dependencies change. It will only run when you tell it to (triggered by event, another query, custom javascript, etc..).

Invoking series of commands in a new tab in cmder

TLDR:
I want to use something like -new_console:t:tabname to open a new named tab in cmder and then transfer focus/control to that tab so that the rest of the commands I'm sending from a Python script run in that console instead. Or, I want to rename a cmder tab from a script running in the console.
DETAILS:
I often have to execute a series of commands in cmder in order to test the latest code from our continuous integration environment. Because there are several applications I often have to have running at a time, it would be helpful for me to have the cmder tabs named according to which application they are running.
The only way I've found to set a tab name from within cmder (apart from manually with mouse clicks) is to do so with the -new_console:t:tab_name command. But that only runs the next command in the newly opened tab, and not all the things that come after it.
I kick off all my commands with a Python script that accepts parameters to let me control which application opens and how things behave. I'd like to do something like this:
os.system('pwd "-new-console:t:' + args.app + '"')
so that a new tab opens with the name of the app I'm about to invoke in it, starting with an indication of the present working directory. But then I'd like all the commands that follow from the Python script to be run in this new tab instead of in the tab used to kick off the Python script. This includes printing some flowerboxed comments, but also invoking a local application server that will continue running.
Is there any way to, as you create a new (named) tab in cmder, transfer focus to that tab so that all future commands run in that tab instead of the initiating tab? Alternately, is there any way from within a cmder console to rename the cmder tab it's running in? That would be just as good.
Thanks!
Thanks for looking, but I found the answer.
In the bottom right corner is a hamburger stack. Click on that and select Settings. In General --> Tab bar, change the Console setting from the default %n to %s. Then the "title" command will change the tab name.

Why won't mysql workbench allow me to execute or create a schema?

I wanna create a schema because I wanna test out tables. I tried to click the "create a new schema", button at the top but it was glazed over where if I click it, nothing happens as if it isn't even there. So after this, I thought "Well I'll try and execute a schema via a statement until then I realized that the execute button is also glazed over. I'm wondering if there's something wrong and obvious I did since I just installed MySQL and have done nothing else in the settings.
You can right-click and create the schema from MySQLWorkbench. The steps are below:
List of Schemas in UI
Right-click, and select Create Schema
Specify the name of the schema to be created
Click Apply, confirm the SQL script in the dialog box, and again click Apply
Note the successful execution of the script
Verify the new schema in the Schemas section in UI

PHPstorm console input not working during debug sessions

I'm using a PHP script which expects user input from a command like fgets(STDIN). The problem is it no longer works in the newest version of PHPStorm (10).
The same works when I run it directly (without debugger enabled) and anything I enter in the console is sent to the script (on direct run).
But during a debug session, when I try to input text at the script's prompt, it does not go to the script. My best guess is that the new REPL feature is overriding user input in console during debugging. I say this because pressing the UP/DOWN arrows opens up a popup with all PHP function names.
It used to work correctly with last version.
How can I send user input to my PHP script with this new version? Am I missing something here?
I'm not sure if this is the same thing, but I was running into this same problem, and I was able to get it working by deselecting the "Use Console Input" checkbox in the PHPStorm Console.
John's answer is perfect.
I want to mention that the Use Console Input is a tiny icon in sidebar of the debug console. I provide you by this image

Where is the MonoDevelop "Application Output" tab?

I've just created a console application. If I run it from the command line, no problem - I can see my output. But if I run from within MonoDevelop, no application output window appears.
I restarted MonoDevelop and that had no effect.
Any suggestions?
And the answer is somewhat illogical (hence why multiple people have this question).
In the Options for the project, on the Run tab, there is a checkbox for "Run on external console." If this option is cleared, the Application Output window will come back when you run the project, and will the become available from the View -> Pads submenu.