The syntax, especially as it is agnostic, is not always 100% transparent. In heavy object management, there should be improvements, and when we have large-scale multitenant environments, the orchestration becomes a bit tedious. But basically, for my use case, it is a tool I recommend 100%. For object management, the problem is the checksum, which has a very strict and sometimes rigid handling. Even if runOnChange is true, helping stored procedures when the code changes, any minor modification or formatting change should be a bit easier. Liquibase flawlessly solves provisioning, maintains consistency between dozens of schemas, has database version controls integrated into Git, has enormous reliability in auditing. However, it lacks native multitenant orchestration, it has a lot of rigidity in checksum management with programmable code, and the use of native SQL within XML does not work entirely well. I give it eight out of ten because it is indispensable and unbeatable for guaranteeing consistency and automatic provisioning in our multitenant architecture. I only deduct a couple of points for the lack of native multitenant orchestration and the occasional rigidity of checksums when modifying MySQL functions.
