Good to know that the filtering is there, the UI for defining the filters can be somehow challenging to get right sometimes. Looking at the tree again, is the level "Schemas" needed at all?
For the per-database settings - actually they can not be set in pgAdminIII - which is one reason to use Dbvisualzer.
The place for setting per-database settings seems reasonable. The settings suggested seems ok, I would also add the Transaction settings.
Hope that you sort it out, but I would say that it is not a show-stopper, since you can always make another connection and tune it to your needs.
Nice to see that the default postgres database setting is there.
For the ApplicationName property, by default it is empty, and it should identify the application, at the connection level, there is no need to set it on the database leve. It could be whatever you want to announce Dbvis as against the database, by default.
One note, if you can't connect to a database, there will be no feedback on that and no visual hint that a connection attempt failed.
Still thinking on a situation with lots of databases in a cluster(perhaps hundreds), could it be convevient to add an option to the connection wizard to switch on the 'show only the database filter option'?
The filtering tree (just as the tree in the Databases tab) has grouping nodes with plural names (Databases, Schemas, Tables, etc) and object nodes (Catalog, Schema, Table etc). Filters can only be defined for the object nodes. I assume that you ask if the grouping nodes are really necessary?
We discussed per-database setting yesterday and came to the conclusion that it would be a major change with lots of risk, so we will not do it for the initial 9.5 release and would like to see requests for this from others before we consider it. As you say, the same thing can be accomplished by creating separate connections for the databases that need tuning.
I have opened a ticket for looking into setting the ApplicationName driver property to a default value.
I will look into the issue with the lack of feedback when a connection cannot be made to an individual database. I assume the typical example would be that the account has no connect privilege?
I have opened a ticket for adding a Show Only Default Database/Schema option to the Connection Wizard.
Thanks for all your feedback!
On the grouping nodes - I am not asking to take avay the grouping nodes. I am just concerned of the tree depth to actual database objects. Since now both multiple databases on one connection and Postgres uses schemas, the tree will be deeper than eg for Oracle (one database per connection) or mysql (no schemas in database). But a flexible database, gives lots of variations!
For the database connection issue, yes, it is precisely the lack of CONNECTION privilege that denies a user access. The SQL commander will show an "Error Alert" dialog when changing the database in the dropdown menu but not when opening a new SQL commander with the database selected it the browser tree. Could the same overlay as for the connection be used as a visual feedback?
As for the per-database settings, I fully understand that it need some more thoughts to be successful and usable.
We've just released DbVisualizer 95.2558 BETA which includes a fix for the problem establishing connections for a database node. Easiest to upgrade is to open Help->Check for Update in DbVisualizer.
thanks for the update! I tested it and I would like to still comment on these, if I may.
Now that that the situation when a connection to another database within the same connection gives a quite verbose feedback - the name, colour of the name and comment on the node is changed. This will stay visible in the database listing, with no possibility to hide it, like e.g. when trying to acess Foreign Servers for a non-superuser.
On the other hand a connection failure just add a failure icon overlay and presents the rest of the information in a hover, which i think is nice.
In the sql commander, there is no visual indications that the database is unnaccessible, as there is for the connection, and after dismissing the first error dialog, there no feedback at all if trying to execute a query on that database. The database node in the browse tree is not necessarily visible at all times, which shows the status.
Ah my bad regarding the Database list in the SQL Commander. It should of course adjust to what databases are really available. I'll open a ticket on this.
Do I understand you correct that the current reporting for database connections that cannot be established in the Databases tab is good enough?
I just wanted to let you know that we have released DbVisualizer 9.5 yesterday with a fix for the issue you reported. Easiest way to upgrade is that you open Help->Check for Update in DbVisualizer to perform the upgrade.
An alternative is that you download from our web site:
Just to inform you that we've released DbVisualizer 10.0. It now shows "dbvis" as the application name in PostgreSQL.
Use Help->Check for Update in DbVisualizer to install the new version or visit the download page on our web. The Check for Update will also indicate whether 10.0 is a free upgrade.