How can we help you today?
DbVisualizer 5.1.1.6 is now available
22 CommentsSorted by Newest First
Roger Bjärevall
said
about 17 years ago
[This reply is migrated from our old forums.]
Re: DbVisualizer 5.1.1.6 is now available
Re: DbVisualizer 5.1.1.6 is now available
Hi,
The first issue with "select 1 select 2 select 3" only showing "1" in each result set tab is a regression bug and will be fixed.
The second request to revert back to the old "Where Filter" appearance is something that we're looking into. Not only by moving back to the old style but rather trying to find out an compromise. Please check the following thread for more discussions on this subject.
http://www.minq.se/forum/thread.jspa?messageID=6486
Thanks for your tests!
Regards
Roger
[This reply is migrated from our old forums. The original author name has been removed]
Re: DbVisualizer 5.1.1.6 is now available
Re: DbVisualizer 5.1.1.6 is now available
Just a couple of things - First and foremost, the SQL:
select 1 select 2 select 3
does not work correctly. On 5.1.1 it correctly shows 3 result tabs with 1, 2, 3 in them respectively. In 5.1.1.6 it still shows 3 tabs but each tab contains 1.
The same applies to stored procedures or other queries that return multiple result sets. I'm using SQL Server 2000 with jTDS in case it's a driver-specific problem.
Secondly, is there a way to switch back to the old behaviour of the quick filter and where filter? I use these extensively and need instant access to them just as 5.1.1 and prior versions have. The dropdown method adds several extra mouse button clicks every time I want to change the filter.
Though many people may appreciate the extra functionality a separate filter window could offer (you could later expand it to configure grouping, summaries, etc) there are many who will prefer an instantly accessible filter like that which was in the old versions. Scouring through the preferences, I have not yet found any way to revert to the old behaviour.
select 1 select 2 select 3
does not work correctly. On 5.1.1 it correctly shows 3 result tabs with 1, 2, 3 in them respectively. In 5.1.1.6 it still shows 3 tabs but each tab contains 1.
The same applies to stored procedures or other queries that return multiple result sets. I'm using SQL Server 2000 with jTDS in case it's a driver-specific problem.
Secondly, is there a way to switch back to the old behaviour of the quick filter and where filter? I use these extensively and need instant access to them just as 5.1.1 and prior versions have. The dropdown method adds several extra mouse button clicks every time I want to change the filter.
Though many people may appreciate the extra functionality a separate filter window could offer (you could later expand it to configure grouping, summaries, etc) there are many who will prefer an instantly accessible filter like that which was in the old versions. Scouring through the preferences, I have not yet found any way to revert to the old behaviour.
Roger Bjärevall
said
about 17 years ago
[This reply is migrated from our old forums.]
Re: DbVisualizer 5.1.1.6 is now available
Re: DbVisualizer 5.1.1.6 is now available
Ronald,
The result of not clearing the data when an out of memory error occur is that you most probably will see another OOME short after which may happen just by clicking in the grid. Instead of presenting partial data it is better to alarm that there is major problem and then the user need to take the next step either by re-phrasing the query or increasing the available memory.
Regards
Roger
[This reply is migrated from our old forums. The original author name has been removed]
Re: DbVisualizer 5.1.1.6 is now available
Re: DbVisualizer 5.1.1.6 is now available
Hi Roger,
it stops, so far ok. It also clears the grid which is a pity. Why not just show what it has fetched ?
kind regards,
R.
it stops, so far ok. It also clears the grid which is a pity. Why not just show what it has fetched ?
kind regards,
R.
Roger Bjärevall
said
about 17 years ago
[This reply is migrated from our old forums.]
Re: DbVisualizer 5.1.1.6 is now available
Re: DbVisualizer 5.1.1.6 is now available
Ronald,
It does stop and it clears the result to make sure you can re-phrase the query or adjust the max rows/cols to continue running. Previously DbVisualizer just hang and you needed to hard kill it.
Or did I miss something?
Regards
Roger
[This reply is migrated from our old forums. The original author name has been removed]
Re: DbVisualizer 5.1.1.6 is now available
Re: DbVisualizer 5.1.1.6 is now available
How do I set the default schema?
If I log in as MYUSER but my application's default schema is MYSCHEMA I want to be able to restrict my view to my application's default schema.
Currently, where I log in as MYUSER, checking the "only show default schema" restricts my explorer tree to showing the MYUSER schema. Other schemas are available in the SQL Editor dropdown.
This never used to be a problem and I can't work out how I achieved this but now it's really frustrating having to keep reseting my schema, even moreso given the number of schemas we have.
If I log in as MYUSER but my application's default schema is MYSCHEMA I want to be able to restrict my view to my application's default schema.
Currently, where I log in as MYUSER, checking the "only show default schema" restricts my explorer tree to showing the MYUSER schema. Other schemas are available in the SQL Editor dropdown.
This never used to be a problem and I can't work out how I achieved this but now it's really frustrating having to keep reseting my schema, even moreso given the number of schemas we have.
[This reply is migrated from our old forums. The original author name has been removed]
Re: DbVisualizer 5.1.1.6 is now available
Re: DbVisualizer 5.1.1.6 is now available
An error occured while performing the operation:
Virtual Memory Problem! The application is running low on virtual memory.
I understand that this happens, I have configured to return 5000 rows and in this particular query I grabbed a clob column that can be anything between 0B and a few GB. It would be nice if dbvis would check it's available memory and stop fetching when it is going to run out of memory.
regards,
R.
Virtual Memory Problem! The application is running low on virtual memory.
I understand that this happens, I have configured to return 5000 rows and in this particular query I grabbed a clob column that can be anything between 0B and a few GB. It would be nice if dbvis would check it's available memory and stop fetching when it is going to run out of memory.
regards,
R.
Roger Bjärevall