Google Cloud SQL VS Liquibase

Cloud SQL: managed relational database service for MySQL, PostgreSQL, and SQL Server. - Source: dev.to / 4 months ago

All cloud platforms are going to have a Postgres database support. Google has something called AlloyDB that looks fantastic for reliability and scalability. Cloud SQL is a bit more standard though. Source: about 1 year ago

Google SQL - not familiar with, does it solve the cons above? Source: about 1 year ago

Cloud SQL with MySQL as I can run it locally and know its queries will be expressive enough (where I am uncertain about Firestore, for instance). Source: over 1 year ago

For example, a Cloud Run Container is a provider for Services, whereas a Cloud SQL Server is a provider for databases. The providers are wrapped in parent containers that encapsulate the capabilities of their children. - Source: dev.to / over 1 year 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: over 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