[abruzzi]

Nice starting point, a few comments/suggestions:

1. When I first make a connection, the application window jumps to full screen size. This is very annoying. I running on a 4k screen with 1:1 pixels, so that is far more real estate than the application needs. Even on smaller screens, I would immediately have to resize the window after I connect.

2. I would like to be able to not provide the database name and allow me to switch from one DB to another using the same connection. (also, currently if you leave DB blank and attempt to connect, it crashes.)

3. 80% of the time I directly connect to my databases with a tool like this, it is not to look at the data, it is to create/drop/modify tables and other design and admin stuff. I'll occasionally use it to test complex queries before putting them in my code, but most of my queries are simple enough that they don't need testing prior to coding. So I'd see this as more useful if it had the ability to simplify the admin stuff. As it is, since I'd need to use pgAdmin 80% of the time, its not compelling to us something else for the other 20%.

[yliang]

Thanks for your suggestions! To replay,

1. I'll fix this.

2. When you switch from one DB to another in postgres, you are essentially making a new connection instead of reusing the same connection[1]. In PSequel, you could create different connection bookmarks for different databases and open multiple connections at the same time in multiple windows.

3. In my company, we write migration scripts (activerecord migration) to modify table structures. We usually don't modify them directly/manually. 80% of the time we use GUI tools just for viewing data and testing out complicated SELECT queries. I didn't realize that many other people's usage patterns are different. Anyway, the feature of modifying table structures is in PSequel's roadmap.

[1] http://stackoverflow.com/q/10335561