Pocket Listen VS Liquibase

Pocket Listen mentions (0)

Liquibase mentions (5)

• How do you guys go about the persistence layer?

  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

• How do you guys go about the persistence layer? (x-post)

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

• Where questioning the scale of a company and its clients its seen bad

  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

• State based change management tool for Snowflake

  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

• Learning SQL and using dll (CREATE,DROP,ALTER)

  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