Comment by brusch64 | Hacker News Reader

Comment by brusch64 | Hacker News Reader

Parent Full thread

For me the biggest reason not to change to PostgreSQL was the sad state of pgAdmin. In my opinion it doesn't hold a candle against the MySQL Workbench or the old MySQL tools.

Sure there are commercial options available, but it is really nice to have some good free or open source tools for a database.

Other than that PostgreSQL looks like a nice database, but I didn't find the "killer" argument to change to it. All the nice SQL syntax changes don't mean too much to me, because I am mostly using an ORM to access the database.

Another thing which isn't working as well on PostgreSQL is master - master clustering. All the solutions I found for PostgreSQL looked inferior to Galera (which has its own pitfalls). On the other hand I think it is far better to have one / two beefy servers than having a cluster of master databases.

pgAdmin is a disaster, and honestly all the tooling around PostgreSQL is not in the best shape. I am currently working on a new cross-platform database admin for PostgreSQL and MySQL - Datazenit[0]. It tries to solve a lot of problems other DB tools have and provides a nice UI on top of it. If you are interested, check it out.

[0] - https://datazenit.com

Looks pretty nice. I am not too fond of web-based database management tools, but it looks good.

One thing I'd like to see in this software would be export to Excel directly (not CSV). I am no big fan of CSV (e.g. Excel can't handle UTF-8 text in CSV files) and think that exporting to xlsx is a tremendous time saver. Exporting to SQL dumps is another important feature - but I see that you have this in your tool.

Looks neat, why not open it up for the community? Your site design just begs for a "Fork Me on GitHub" link.

> For me the biggest reason not to change to PostgreSQL was the sad state of pgAdmin. In my opinion it doesn't hold a candle against the MySQL Workbench or the old MySQL tools.

Oh I agree, but for many projects its not really an issue.

With Django, you can use the Django admin for GUI changes and the REPL shell for more programatic changes.

On my Django projects, I've never had to actually write SQL.

You never had to copy data from a test database to the productive database or the other way around ?

I am using MySQL Workbench all the time for tasks like this.

Reply on news.ycombinator.com