I recently started using Postico after a teammate recommended it, and I have found it simple and easy to use. You can try it out with a seven-day free trial before deciding to buy the Pro version.įor my purposes, the query-centric design was inconvenient, so this was not my client of choice. However, working with multiple schemas can be confusing, as they are not separated. Overall, the organization is straightforward. One downside of this client is that it is specific to PostgreSQL, making it less likely to be useful on the next project. You’ll have syntax highlighting and autocompletion of table and column names, making it easy to crank out queries. For example, navigating to a table generates a query for the first 1,000 items by default. I found it to be less of a database viewer and more of a query building tool. If you are mostly looking to write queries, SQLPro for Postgres could be a great fit. Support for multiple database management systems: I just want one client for all of my projects.

Content and structure: Shows me what I need to know.Navigation: Easy to switch between tables and queries.To save you the trouble of downloading and testing them for yourself, I’m going to walk through of a few of the best. After experimenting with a few database clients (SQLPro, Postico, and TablePlus), we quickly noticed that some are better for our needs than others. On my current project, we’re constantly investigating data, switching from table to table, and writing queries with our PostgreSQL database. When development relies on database interaction, few things are more frustrating than a database client that gets in the way.

Tableplus tutorial