Liquibase vs Mycli: What are the differences?
Liquibase: Source control for your database. Developers store database changes in text-based files on their local development machines and apply them to their local databases. Changelog files can be be arbitrarily nested for better management; Mycli: A CLI for MySQL with auto-completion and syntax highlighting. Mycli is a command line interface for MySQL, MariaDB, and Percona with auto-completion and syntax highlighting.
Liquibase and Mycli can be categorized as "Database" tools.
Some of the features offered by Liquibase are:
- Supports code branching and merging
- Supports multiple developers
- Supports multiple database types
On the other hand, Mycli provides the following key features:
- Auto-completion as you type for SQL keywords as well as tables and columns in the database.
- Syntax highlighting using Pygments.
- Smart-completion (enabled by default) will suggest context-sensitive completion.
Liquibase and Mycli are both open source tools. It seems that Mycli with 7.75K GitHub stars and 475 forks on GitHub has more adoption than Liquibase with 1.78K GitHub stars and 1.09K GitHub forks.
What is Liquibase?
What is Mycli?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Mycli?
What are the cons of using Mycli?
What companies use Mycli?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Flyway vs Liquibase #Migration #Backwards-compatible
We were looking for a tool to help us integrating the migration scripts as part of our Deployment. At first sight both tools look very alike, are well integrated with Spring, have a fairly frequent development activity and short release cycles.
Liquibase puts a lot of emphasis on independence with the DB, allowing you to create the scripts on formats like JSON and YML, abstracting away from SQL, which it's also supported. Since we only work with one DB type across services we wouldn't take much advantage of this feature.
Flyway on the other hand has the advantage on being actively working on the integration with PostgreSQL 11, for it's upcoming version 6. Provides a more extensive set of properties that allow us to define what's allowed on what's not on each different environment.
Instead of looking for a tool that will allow us to rollback our DB changes automatically, we decided to implement backwards-compatible DB changes, for example adding a new column instead of renaming an existing one, postponing the deletion of the deprecated column until the release has been successfully installed.