Postico VS Liquibase

Since you mentioned it, I was always curious if the team behind TablePlus were/are connected to the team behind Postico [1]. The UIs for both (at least before Postico 2) are almost identical. [1] https://eggerapps.at/postico2/. - Source: Hacker News / 7 months ago

Postico is a native Mac app for Postgres databases (and some compatible databases including Amazon Redshift, CockroachDB, Greenplum, and others). It's a Mac-only app, and the UI reflects it. The person behind Postico is the same developer who built postgres.app, which starts a Postgres server on your Mac. - Source: dev.to / 7 months ago

Sequel pro could be compared with postico2 as far as native look and feel go - https://eggerapps.at/postico2/. - Source: Hacker News / 8 months ago

Also I recommend you using Postico or Table Plus with your Relational Databases, believe me it's a lot more easier to surf through your DB if you have tool like this. - Source: dev.to / over 1 year ago

Postico is macOS PostgreSQL client for reading data, doing basic manual data entry and editing your database structure. - Source: dev.to / almost 2 years ago

As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: about 2 years ago

I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: about 2 years ago

Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: about 2 years ago

I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:. Source: about 2 years ago

Nowadays I prefer to automate database updates and deployment, using Liquibase and its relational database vendor agnostic syntax for that. Especially on production systems. But on local dev environments, I can still use the occasional SQL in a pinch. Source: over 2 years ago