Since 2018.2, "select current_database() as a, current_schemas(false) as b" obscure last status
Answered
Since 2018.2, when I execute some commands (but not all, for some reason), there is often an additional command executed by the IDE: "select current_database() as a, current_schemas(false) as b".
Whilst in itself this doesn't necessarily cause problems, it obscures the result of the most recent response message as shown in the status bar at the very bottom of the window.
For example, I see "completed in 20 ms" where I'm expecting to see something like "25 rows affected in 100ms" or whatever.
Is this a bug? I'm actually seeing this in PyCharm 2018.2 but I believe it's best to report issues relating to the database plugin stuff under DataGrip.
Please sign in to leave a comment.
I just saw that this is newly introduced in 2018.2 as a feature! Including all SQL queries in the output whether issued by the user or by the IDE. Please, please please, can you make this configurable? I have no interest in seeing the system generated stuff and it obscures my 'at-a-glance' view of the records and duration for my own queries (often, not always).
Thanks!
One can fold mentioned lines. Invoke context menu and select `Fold Lines Like This`:
My context menu doesn't include that. I'm actually in PyCharm but raising here because it's DB-related.
If I were able to get that folding to work would that stop it displaying the message in the very bottom left of the window?
I can confirm it does it in DATAGRIP as well. Very hard to find the results of executing a SQL statement when the IDE shows results for queries not executed by the user. Would not have upgraded if I had known that this was a "feature", as it provides not value and cost a little bit of time for each SQL command to locate the results.
Even if you "fold lines" you still get something like:
sql> COMMIT
[2018-08-15 13:38:20] completed in 45 ms <1 internal call>
[2018-08-15 13:38:20] completed in 46 ms
If it is an internal call why do I need to see it in my output?
@Kpelca I agree. @vasily I don't think this should have been marked as answered. I've raised a YouTrack issue here:
https://youtrack.jetbrains.com/issue/DBE-6905