Tatiana Fernández

Hi @aburakc, thank you for reporting this issue. I've been able to replicate it with the CLI, so it's a liquibase-core bug. I'll be leaving this ticket open for the...

Hi @slicerahul, thank you for reporting this issue. I've been able to confirm that this is a problem for Liquibase versions 4.25.1 and 4.26.0. Specifying the diff type `column` does...

Hi @mtagliaf. I have been able to replicate what you're reporting: running `liquibase update` with the code you've provided creates a procedure that's defined as follows: ``` create procedure dbo.TestProcedure...

Hi @ShadowNinjaHunter, thank you for reporting this issue. I have been able to replicate it with Liquibase v4.26.0, and with both PostgreSQL and SQL Server. However, SQL Server doesn't output...

Hi @SabeetaBhandari, we were aware of this problem, and it's fixed by versions 4.25 and onwards. Could you try updating your Liquibase version and re-running your program? Let me know...

@kevin-atx here's a summary of the problem as I understand it: In databases like MySQL, to modify a column's name or datatype you need to re-define the entire column, including...

@MarcioMonego do you agree with my write-up on the problem? If you'd be willing to create a PR to solve this, our development team will be available to guide you...

Hi @UWollesen, thank you for reporting this issue. I tested it using the changelog and csv file you provided, and with different databases in order to determine if it's a...

Hello @mattjudge , thank you for letting us know about this issue. I was able to recreate it, though I'm not sure if this is a bug that should be...

Hi @ttekampe, thank you for reporting this issue. I've been able to confirm that this still occurs with Liquibase v4.26.0. **With one line** file.sql: ``` SELECT * FROM Book; ```...