Schema doesn't filter by schema

I created a new connection, and set the schema to public:

But I’m still seeing tables from all schemas (including the PG ones, which are a lot):

BTW: Good job on the GUI, I can’t believe I missed something this well polished. Except for these two bugs, this is great stuff!

[maxcnunes]

The trick thing about the multiple database types support is that when we need to add a new feature or changing an app behavior, you have to take in consideration all the other database clients. Some times, we need to keep the UI or even internal implementation simpler so it can have a better consistency over all databases clients. That said, I guess we didn’t grouped by schemas because not all dbs have schema support. So keeping schemas in the same level with tables was the best approach to ensure UI and internal implementation consistency over all dbs. But I’m not against this feature if grouping the tables or schemas would really improve the UX. I just don’t want to spend time in this feature since the current implementation is working fine for me 😃 If anyone else is interested to work on that I could help with any development questions.

[lordjavac]

How about grouping objects by schema in the lists. Then we can expand the schema we want to browse but still have access to the others. So, under “Tables” we can have “information_schema”, “pg_catalog”, “public”, and any other applicable schemas. It think this would help declutter the lists while retaining the desired access.