Start a new topic

DbVisualizer 5.1.1.5 is now available

[This topic is migrated from our old forums. The original author name has been removed]

Hello, DbVisualizer 5.1.1.5 is now available for download in the early access section: http://www.minq.se/products/dbvis/eap In addition to the change log for this EA has the following features been fixed. (They were poorly integrated in the previous EA version): - Table data editing with the inline and form editors - Creation of monitors in the Data tab - "Browse row in form" didn't work Best Regards Roger

[This reply is migrated from our old forums.]

Re: DbVisualizer 5.1.1.5 is now available
Georg, Sorry I missed to answer your query about error location in Oracle statements. > I know this is OT with respect to this thread, but > are there any plans to make the editor tell the user > where the errors occurred in an SQL statement (I > thought it might not be possible because of > limitations in the (Oracle in my case) JDBC > implementation, but I had a look at Oracle's SQL > Developer and it does this even when using the type 4 > driver) ? Nobody would be shocked about this :-) We haven't reviewed the latest versions from Oracle lately so I cannot comment whether this has been improved. I am not surprised the Oracle tools have this and have had for a while, after all they know about all their inner secrets :-) Seriously, if their tools are using the standard type 4 driver then it is a bit surprising as there are no public API that can be used to get information such as error location, etc. We'll look into this again. Regards Roger
[This reply is migrated from our old forums.]

Re: DbVisualizer 5.1.1.5 is now available
Georg, Thanks for your observations. You mention that you need to close the dialog after pressing "Use Filter"? Pressing "Use Filter" should apply the filter and close the dialog in one step. We will consider a change/enhancement of the filtering feature in general to satisfy users that like the old style. Related to this: would a solution with a text field that supports auto completion of column names be an option i.e. the text area showing the complete filter in the previous version? The idea is to offer a text area that is used to browse and optionally edit the filter. This can be used by advanced users to do quick edits of the filter but still keep the UI less cluttered from buttons and fields. Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: DbVisualizer 5.1.1.5 is now available
Roger, I continued testing with 5.1.1.6, now that the live-saving Stop button is back. Having used the new quick and where filter dialog quite a few times now during daily work I can see the value in making these persistent (although I never even got near using the sort section, this feature apparently does not fit into my usage pattern). I am working in manufacturing and many times a day I click the Data tab and enter something like: facility = 'Foo' and lotid in ('first_id','second_id','third_id') for various tables. These where conditions are almost all one-time shots that do not need to be remembered (would even be considered as noise). Usually the list of lot ids is edited several times before moving on to the next task. For this scenario the new filter handling is a real pain, in particular, closing the dialog after clicking "Use filter". Regards, Georg
[This reply is migrated from our old forums.]

Re: DbVisualizer 5.1.1.5 is now available
Ronald, Ok, got it. Copy via key binding seem to work fine if the result set grid is edit enabled while it doesn't for read-only result sets. I'll look into it. Thanks! Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: DbVisualizer 5.1.1.5 is now available
Roger,

It does work for the data grid in the object view, not from the result grid in the sqlcommander.

regards,
R.
[This reply is migrated from our old forums.]

Re: DbVisualizer 5.1.1.5 is now available
Ronald, Does the copy key binding work better in 5.1.1.6? Regards Roger
[This reply is migrated from our old forums.]

Re: DbVisualizer 5.1.1.5 is now available
Ronald, The way the SQL Commander works now is actually a bug :-) The absence of the Stop button resulted in that several SQL editors can be launched concurrently. Since multi executions is not properly supported there may be situations when errors occur. The ability to run several SQL scripts at the same time is the last major enhancement for the next official version so expect to see this supported soon. Regards Roger
[This reply is migrated from our old forums.]

Re: DbVisualizer 5.1.1.5 is now available
Hi Ronald, You need to double click the red puzzle icon in the grid to open the cell editor. Another way is to double click the thumbnail icon in the form editor to open the cell editor. Then in the cell editor you can export and print the image. Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: DbVisualizer 5.1.1.5 is now available
I could be wrong but did we have an image export option before 5.1.1.5 ? Now I miss it ... R.
[This reply is migrated from our old forums. The original author name has been removed]

Re: DbVisualizer 5.1.1.5 is now available
I found that sql commander now only locks the current connection when there is a long running sql active. That is good.With a few connections open and in one running a very longrunning qry I accidentally selected such an active connection in sql commander which caused dbvis to lock the gui completely. Can that be changed ? Maybe that - locked - connection can be made unselectable in the gui ?

thanks,Ronald.
[This reply is migrated from our old forums. The original author name has been removed]

Re: DbVisualizer 5.1.1.5 is now available
Roger, thanks for outlining the motivation for the change. But: it is already very easy to hide the visibility of the quick and where filter using the Data tab toolbar buttons. My preferred solution would be to continue with the existing approach, just placing the sort section below the other sections and add a new toggle to show/hide it, and may be a button for hiding all three sections (plus a keyboard shortcut) with one UI gesture. On my UXGA screen the space for the data grid would not be a problem. As to the filter history: I was referring to pre-5.1.1.5 functionality. I have not tested the new features in 5.1.1.5 yet (thanks for all the hard work!). I know this is OT with respect to this thread, but are there any plans to make the editor tell the user where the errors occurred in an SQL statement (I thought it might not be possible because of limitations in the (Oracle in my case) JDBC implementation, but I had a look at Oracle's SQL Developer and it does this even when using the type 4 driver) ? Nobody would be shocked about this :-) Regards, Georg
[This reply is migrated from our old forums.]

Re: DbVisualizer 5.1.1.5 is now available
Georg, The previous integrated filter solution had several problems. In combination with various enhancement requests it was quite difficult to solve it and still keep the GUI intuitive and not too cluttered. Another important issue was the fact that both the quick filter and the where filter took a lot of space from the data grid (a lot of people complained about this). As always it is difficult changing existing features since some prefer how it use to work while other applaud the change. The only option (more or less) a tool vendor have is to make sure all camps are satisfied by making it configurable. You say: "there is some form of filter history (right mouse button click), although not persistent across sessions". All filters are saved between sessions and even reloaded whenever you hit that table again (if the filter was previously active). Doesn't this work for you? We've looked into using a docking framework and split most of the GUI into separate dockable windows. That would certainly improve but this kind of change would however result in some users loving it while others will enter shock mode... Regards Roger
[This reply is migrated from our old forums. The original author name has been removed]

Re: DbVisualizer 5.1.1.5 is now available
Roger, making the dialog non-modal would surely help a lot. Imagine the incessant dialog popping up and down until all those missing commas or wrong single quotes have been fixed. Of course the additional features are nice, but I am uncertain as to why this has to be connected to a (at least for me) fundamental user interface change. Having both the Data tab and the SQL Editor has always been a strength of DbVisualizer, the first one being used for the quick lookup and the second one for serious query development. With 5.1.1.5 the "quick lookup" is much less quick and smooth. And there is already some form of filter history available (right mouse button click), although not persistent across sessions. Until now no continuous dialog opening and closing during the standard workflow of filtering and querying existed in DbVisualizer. Every now and then I have to open the Bookmark window, but that's all. How about using a docking framework? (Actually I have been moving around the filter dialog desperately for some time hoping that the GUI would give me a hint where I can place it...). I will have a second look at 5.1.1.5, but I am still a bit shocked. Regards, Georg
[This reply is migrated from our old forums. The original author name has been removed]

Re: DbVisualizer 5.1.1.5 is now available
How about showing the active filter text between the buttons and the grid? Or in the status bar of the grid (there it would have to be abbreviated, so i would prefer the first proposal)? I like the fact, that the filter keeps active for a table while switching between different tables (and even over program restarts! Nice :-) ) and that a history of filter statements is maintained, but i'm missing the visibility of the active filter statement too (but not this much: TOAD has nearly the same mechanism for filtering, but without the history...) Bye, Peter
[This reply is migrated from our old forums.]

Re: DbVisualizer 5.1.1.5 is now available
Georg, Yes it is now a modal dialog and it cannot be changed. We'll look into making it non modal but it will still be a separate window. Regards Roger