Liquibase can be improved by helping developers who have never used it before to understand change logs, change sets, contexts, and labels, which takes time. The documentation is good, but there is a gap between reading the docs and actually being confident with it. I would appreciate more sophisticated pipeline analytics out of the box without having to set everything up manually.
I believe the official documentation of Liquibase could be more detailed and comprehensive. Although Liquibase has substantial community support through open source tutorials and Stack Overflow resources where people can find solutions, the documentation could be simpler and more explanatory.
Liquibase could be improved in several ways. Some facilities could be enhanced, and for first-time users, it could be more intuitive rather than overwhelming.
Liquibase can be improved by addressing the issue that changelog files could conflict with Git if they're not modularized properly. While we create one file per feature, rollbacks are not magical and require significant consideration, and large diff operations can also be very slow, affecting performance. We only use MySQL for now, so there's nothing related to any exotic database features, and we're not consuming anything on that side either.
Liquibase is a solution for database change management that automates scripts and integrates with MySQL, MSSQL, and PostgreSQL. It simplifies database syncing, reduces risks, and supports SQL validation while effectively tracking schema updates in DevOps environments.Liquibase offers a robust platform for automating database changes, effectively supporting integration with CI/CD pipelines. Users benefit from its capabilities to manage changesets and changelogs, ensuring controlled rollbacks...
Liquibase can be improved by helping developers who have never used it before to understand change logs, change sets, contexts, and labels, which takes time. The documentation is good, but there is a gap between reading the docs and actually being confident with it. I would appreciate more sophisticated pipeline analytics out of the box without having to set everything up manually.
I believe the official documentation of Liquibase could be more detailed and comprehensive. Although Liquibase has substantial community support through open source tutorials and Stack Overflow resources where people can find solutions, the documentation could be simpler and more explanatory.
Liquibase could be improved in several ways. Some facilities could be enhanced, and for first-time users, it could be more intuitive rather than overwhelming.
Liquibase can be improved by addressing the issue that changelog files could conflict with Git if they're not modularized properly. While we create one file per feature, rollbacks are not magical and require significant consideration, and large diff operations can also be very slow, affecting performance. We only use MySQL for now, so there's nothing related to any exotic database features, and we're not consuming anything on that side either.
We were not able to delete some of the tables because of a security issue.
I can't think of any features that are lacking. So far, it's been quite a good solution for us. And the vendor continues to enhance the product.