More Improvements For SQL Console

On 3/14/12 9:27 PM, opticyclic wrote:

I didn't want to reply to the original thread as it is quite old now (http://devnet.jetbrains.net/message/5225204), however, I feel that there are still a few things to improve on.

>
>

1. Ctrl-Enter still doesn't execute. This is the shortcut in SquirrelSQL, Oracle SQL Developer an DBVisualizer I believe.

It really works for me.
Please check your Keymap settings for "Database Support/Execute" action.
This shortcut also works directly from editor after any "Run Query in
Console" intention action usage.
Selection is taken into account thus covering point 2 as well.

2. You still have to execute the entire script instead of the highlighted text.

See above.

3. There should be an option in the context menu of tables to create a select statement. See SquirrelSQL for example.

Missing. Ticket welcome.

4. The results should be exportable to csv or Excel.1. The current Select All, Copy seems to use a single quote as a delimiter!

A limited set of export properties is available in console properties.
Properties action is present in a console tool window toolbar on the left.

5. There doesn't appear to be a way to limit the number of results returned. See SquirrelSQL for a tickbox and 100 by default.

"Result set page size" option in console properties. See above.

6. The load time of tables is still slower than other clients. Although maybe not as slow as it was previously  http://devnet.jetbrains.net/message/5225204#5225204

Currently we do not use native APIs or information schema. Known issue.

Fortunately with Sybase and DB2 we now have the whole pack of SQL
dialects and we are able to address all SQL console issues as they
really should have been.