In general I agree with Nikolai that it is helpful to have ability to use the navigation panel and other tools for my database when I haven't access to others.
I'm sure that my case is impossible in the current pgadmin version. After all searches I suggested to use other tools to the customer.
We opened that some other tools (razorsql, sql developer, navicat, etc) have the same behavior. Then we finally found a suitable tool.
Would be quite difficult. And I completely dislike the idea.
If you only need the SQL editor, you can already do this by launching PgAdmin directly with the SQL tool.
I'm not sure what you mean by "directly with the SQL tool"? Anyway. It could be usefull not only for just typing SQL. Even when access is essentially restricted to some specific database, the navigation panel could still be usefull to show objects within that specific database and fetch their properties etc. This is done through pg_catalog so it should work fine I suppose? I actually can't see what's so wrong with this setup (other than someone would obviously have to spend some time and effort to develop patches) In fact, that is exactly the usage pattern I have with pgadmin most of the time: connect to a specific database and _stay_ _within_ that database.
