PgAdmin 4 v1.0 released
pgadmin.org
pgadmin.org
I am using the older version and is one of my favourite PostgresSQL GUI tools.
Another tool victim of the craziness to pack web pages as desktop applications and being written in Python and JavaScript is already an indication the performance you describe.
So I will stick with the current version until I find a good alternative, checking Valentina Studio now.
There's a commercial license i'm glad to pay for, and the free(lite) edition is just fine for most needs
http://www.sqlmanager.net/en/products/postgresql/manager/mat...
(it might totaly sound like a commercial "happy customer" review, and it actually is)
PGadmin was functional, I'll give it that, but it paled in comparison to MySQL's tools. If this can speed up development and make it better then I'm all for it.
Maybe they could integrate this[1] into it?
[1]: https://www.sequelpro.com/ [2]: https://github.com/sequelpro/sequelpro/issues/362
Postico for Mac is also very nice to use:
Having worked with MSSQL for years, MS hit the right spot with Management Studio. It's an UI focused on writing SQL, and any wizard has a "Generate SQL for this" button. It let me write huge SQL files, save them, reopen then and run them. When I found dbForge Studio for MySql, I felt at home. I wish postgres had something like that.
Last week I went through ALL the GUIs in the postgres wiki page and found nothing good. Valentina Studio and EMS are good, but not great. EMS has a lot of features, but honestly it bothers me it cannot even use the default system font in windows, the environment it's built to run on. It's like it's stuck in 2002.
If I could sum it up, the thing I miss the most is being able to work with SQL. I want the first button in the toolbar to be a "New SQL Query" that opens a huge editor that lets me write and run SQL. Not a "new database", not "new project". Amazingly, most postgresql UIs are simply terrible at writing and running sql.
It's like postgres uis are like the PHP of database UIs: people that like it have no idea how bad they are, and the very few people go elsewhere to see how much better the world is outside.
I have used other database management tools. To me, it seems that pgadmin3's New Query window behaves pretty similarly to Microsoft's New Query window. I've used several other database GUIs (SQLyog, others) but there are none that, IMO, are night-and-day better than pgadmin3 for my basic uses.
I definitely believe that pgadmin3's interface for adding columns to tables is onerous, but that doesn't happen very often since MVC frameworks brought schema definition as code into the mainstream.
Helps a lot if you deal with many databases.
- ER data modeling.
- Visual representation of the database objects
- Completion while typing and visual representation of SQL errors
- Ability to change anything on the database without having to know by earth all SQL differences across different RDMS
- Exporting data into various formats
A few examples,
http://www.valentina-db.com/en/valentina-studio-key-features
I just want some good GUI for data entry. For querying, command line already covers like 90% of my needs. I don't mean something like Access for postgres or a full-fledged CMS which will mess with my beautiful, hand-crafted schema - I need just a table view with BLOB support (like choosing a file and maybe showing a preview if image) and foreign key support (like autocomplete).
Does anyone know a tool like this? I can pay - just need to be able to install it on my machine.
If non-PG is fine, then maybe sqlitebrowser.org?
You'd want to grab the latest nightly though, as our foreign key constraint handling needs improvement, and there is good progress with that in the nightly builds. :)
To view blobs, just keep the "Edit Database Cell" dock open (it's under the View menu).
Any time you select a cell with an image in it, the image will be displayed in that dock. You can just leave that dock open and keep working on stuff in the main table area if you want.
will keep using the excellent http://www.heidisql.com/
probably not as fully featured for serious admin tasks, but it's fast, lightweight and works well for daily db tasks for SQLserver, mysql variants and postgres. i encourage everyone to donate.
However I am not very keen on using it for Postgresql until that "experimental" flag is removed.
pgadmin3-1.22.1.zip: 12.7MB
pgadmin4-1.0-x86.exe: 82.5MB
First impressions:
Much, much slower to load than pgAdmin3.
>The software has the look and feel of a desktop application
No it doesn't. I don't think the person who wrote this even knows what "the look and feel of a desktop application" means. I can tell within a second of it starting that it's not a native application, which basically by definition means it doesn't have "the look and feel of a desktop application". In fact, I have no idea what they are talking about when they say "the look and feel of a desktop application." I can't detect a single thing which seems to imply any effort in this regard. I would be genuinely interested to know what on earth they think in pgAdmin4 has "the look and feel of a desktop application".
I open the preferences window. The preferences "window" is not a window. It's an overlay in the main window, which cannot be moved. Context "menus" are similar, and thus cannot exceed the bounds of the main window, which is not how they are supposed to work. Not even the windows, beside the main window, are real. "The look and feel of a desktop application"?
What the UI does scream is not "a desktop application", but Bootstrap.
I try to connect to a server. The tree view "+" icon for expanding a level in the hierarchy has a loading spinner superimposed over it, which is not a convention I recall ever seeing before. The loading spinner doesn't end. It never becomes possible to do anything with the server. I have to restart the programme and try again. This time it works.
When I expand the items in the tree view for the first time, the icons for the tree view items are initially absent and flash into place, as the images are loaded.
Compared to pgAdmin3, it's horrible and borderline unusable. It's also slower.
>...and vastly improves on pgAdmin III with updated user interface elements, >multi-user/web deployment options, dashboards and a more modern design.
It's slower to respond. It's slower to start. It uses more resources. It's a godforsaken web application. It is infinitely less like "a desktop application" than pgAdmin3 because pgAdmin3, unlike pgAdmin4, was a desktop application.
There are also stupid animations, such as fade effects, which constitute completely unnecessary delays to what should be a functional interface.
For some reason context menus sometimes open a substantial distance from the mouse cursor.
Even for a web application, there are parts which are quite poorly styled.
If they wanted to develop a web application, fine, but why call it pgAdmin? This is not in any meaningful sense a "pgAdmin 4". It's a completely new, different, IMO inferior product that someone has decided to call "pgAdmin 4" in an attempt to terminate pgAdmin3. So I reject the premise that "pgAdmin 4" can be considered a legitimate successor to "pgAdmin 3", because it isn't. It's something completely different, falsely purporting to be pgAdmin. If they decided they wanted to make a web-based PostgreSQL administration tool, then do that. If they don't want to maintain a native application anymore, they could at least state as much and not release this product-killing copout absurdly spun as some sort of improvement or natural successorship.
Even the authors seem to implicitly admit it's a different product, what with the default install directory: "C:\Program Files (x86)\pgAdmin 4\v1". v1 of v4.
But no, they opted for a full rewrite with messy bowl of jQuery UI plugins and second-long animations.
I don't really use pgAdmin anymore (psql for the win) but, was hoping that this would be nice: it's not. Apparently my experience is mirrored by many others (I wanted to see if it was just me or not)... oh well.
They'd hit a problem where signing wasn't working, which turned out to be because the framework bundles inside the .app were in an older format. The bundled OSX "codesign" util was just barfing.
Gave them a working shell script to fix the problem, which they'll probably adjust / clean up + add to their build process.
So, next releases shouldn't have this issue. :)