Several improvements for DbVisualizer

Andreas, Thanks for the feedback. > {quote:title=Andreas Klaus wrote:}{quote} > 1. When SQL Commander has only one window open (main window), the command "Close current SQL editor" clears the window with the SQL text. But the log, result sets and DBMS output in the lower part should also be cleared We will re-design the way editors are organized in a future version and your request will be considered during that work. > 2. The position of the separator bar between the SQL text and the result sets should be saved and used when opening new editors. I register a feature request for this. > 3. The grid column chooser in the object view should have a possibility to save several "views" on a table which can be quickly selected by name. For example, if you have a table with weather data, the view "Rain" could show all columns concerning rain, the view "Sun" could show all colums concerning sunshine and so on. This is something we have on the list already. I'll add your vote for it. > 4. The grid column chooser should have a quick filter just like all grids. I'll register a ticket for this as well. > 5. There should be a setting for lowercasing or uppercasing auto completion text in the filter in the object view just like the setting for auto completion in the SQL editor. This could be configurable separately, or auto completion could be taken one level up in the Tool Properties window and the setting used both for the object view and the SQL editor. These filters are primarily used to filter only what should be displayed in the scope of DbVisualizer and the Data tab. Designing and executing SQLs in the SQL Commander is however somewhat different as these SQLs most often end up being incorporated in other systems and applications. Can you please give an example when auto upper/lower-casing of completed column names is of any interest in the scope of the Data tab? Thanks again for your feedback! Best Regards Roger

Andreas, Thanks! I will register a ticket for this. Regards Roger

Hi Andreas, The Max Rows/Chars will be fixed in the next feature version. The "Stop" request is related to two different scopes: in the Object View Data tab it stays at showing the result set being fetched up to stop was requested with the addition of the bubble message. The reason is that the Data tab only have a single result set to show and there is no log. The SQL Commander however is supposed to manage any type of SQL and also scripts with multiple SQLs. When the user press Stop it is better to always switch to the Log so that the user must review what was stopped and the result of doing so. This is by design. Best Regards Roger

Hi, Just to inform that the Max Rows/Max Chars is now fixed in the latest DbVisualizer 8.0 version. Regards Roger

Andreas, Just to inform you that the "Case for Auto Completion" and "Delimited Identifiers" tool property settings are now also respected in the Table Data filter. Give it a try in the latest BETA of the upcoming 9.0 version. http://www.dbvis.com/download/beta/ Regards Roger