Tatiana Fernández

Hi @qnkhuat, thank you for reporting this issue. I've tried running the scenario programmatically and using a Maven goal, but I haven't been able to replicate it. Here's what I...

Hi @ramarro123 I ran `liquibase validate` with the changelog file you've provided, and this was the output: ``` Starting Liquibase at 12:06:52 (version 4.25.1 #690 built at 2023-12-18 16:29+0000) Liquibase...

@vtheuer this is a different issue, as it's not exclusive to the yml format. It's a good catch - the validator doesn't detect new changes if they're wrongly placed inside...

Hi @ShadowNinjaHunter, thank you for reporting this issue. I've been able to replicate it with Liquibase v4.25.1 and v4.26.0. Currently Liquibase doesn't support aggregate functions for the `drop-all` command. I...

Hi @evgenkolesman I'm having some trouble reproducing this issue. I don't understand what information goes where. Could you provide more detailed step-by-step instructions? If you already know how to fix...

@MalloD12 this is what is being generated when running `liquibase update-sql` with this fix and the changelog: ``` databaseChangeLog: - changeSet: id: 1 author: tati changes: - createTable: tableName: person...

Hi @Mangooos and @richardo-kusuma, could you share your `` tag? This could be related to the `.xsd` files specified.

I tested this using the CLI and couldn't replicate the bug - here are the two workflows I tested: 1. Running the changeset with v3.2.2, then with 4.11.0, then with...

Hi @omarmahamid, I need some more information in order to effectively test this. 1. I understand that with version 4.0.0 the output is located in the path specified in the...

@omarmahamid I see what you mean. In summary, up until Liquibase v4.19.0, if the `outputDirectory` was set to `/Users/(project path)/target/generated-docs`, the resulting file structure would be as follows: projectPath .|_...