[jakobegger]

The unfortunate reason for that is a data editor can be whacked out in a couple of weeks (well, at least an MVP).

Making object editors takes a lot more effort, especially considering all the different objects PostgreSQL has: schemas, tables view, materialized views, indices, functions, sequences, etc.

I'm struggling with this myself. I'm currently trying to add object editors to PG Commander, and it's months and months of work. I wanted to have a table structure editor in PG Commander 1.0, and now, more than a year later, I'll finally be able to deliver a basic table & view editor in version 2.0 -- you can try a prerelease here: https://eggerapps.at/pgcommander-prerelease/

[bsg75]

In my case, I almost never edit an object in a UI, but I often view it. Sometimes in a grid (ex. table columns in a grid of type, nullability, default, etc.) or as a single view of all the DDL for the object. I don't trust UIs to edit objects, but they can make the work of creating ALTER scripts much easier.

The latter is where PgAdmin is most useful for DB objects. The DDL view not only shows me things like CREATE TABLE/VIEW/FUNCTION etc., but also shows dependent objects such as constraints, indexes, permissions in the same window. Most of the JDBC based tools do not.

Graphical explain plans can be very nice to have, along with status views that make things like pg_stat_activity easy to consume in an actively refreshing compact view.

[EddieLomax]

Awesome to hear, Jakob-- I recently purchased PG Commander after a couple of months of using it, so a "free" update to 2.0 is awesome. Thanks for your hard work on the app-- it's my default PostgreSQL client.

[radimm]

Great work! Please, tweet more or email customers more about things like 2.0 Alpha! Would love to start testing this sooner.