[This topic is migrated from our old forums. The original author name has been removed]
1. Editing in the Result Set grid in SQL Commander is possible when only one table is referenced in the SQL. When using shortcuts (for example, CTRL-ALT-S for inserting the current date), the save icon is not enabled. CTRL-Z (Undo) also doesn't work. Both functions are working in the object view.
2. The border decoration which shows development, test or production is duplicated when executing an SQL (one border around the whole SQL commander, and a duplicate border around the resultset).
3. The icon for the primary key is not considered when calculating the column widths for auto resize.
Andreas,
Thanks for your feedback.
> {quote:title=Andreas Klaus wrote:}{quote}
> 1. Editing in the Result Set grid in SQL Commander is possible when only one table is referenced in the SQL. When using shortcuts (for example, CTRL-ALT-S for inserting the current date), the save icon is not enabled. CTRL-Z (Undo) also doesn't work. Both functions are working in the object view.
We will look into this.
> 2. The border decoration which shows development, test or production is duplicated when executing an SQL (one border around the whole SQL commander, and a duplicate border around the resultset).
This is intentional since a result set may be pinned and kept between executions. All result sets and their connections connection mode may also differ since two result sets may be the result of running a query with two different database connections. So each result set have their border if mode is one of Production or Development.
The outer border represents the mode of the currently selected database connection in the editor.
> 3. The icon for the primary key is not considered when calculating the column widths for auto resize.
This will be fixed in the next version.
Thanks again!
Best Regards
Roger
Roger Bjärevall
said
over 13 years ago
[This reply is migrated from our old forums.]
Re: Several small issues in SQL Commander
Hi,
Just to inform that this is now fixed in the latest DbVisualizer 8.0 version.
Regards
Roger
anonymous