Tatiana Fernández

That makes sense. We currently have a fix to a similar problem but only for MSSQL database instances, it can be found in the Liquibase source code. For version 4.25.1,...

Hi @goughy000, thank you for reporting this issue. I agree that the behaviour should be consistent, and I believe this is more a program bug than a documentation error. Here...

Hi @thousmile, could you add some steps to reproduce this issue so I can test this more effectively? Thanks!

@malikin in general this looks great! There are just two things worth mentioning: 1. By default it's outputting a JSON format, but it should be a text. Using `-Dliquibase.snapshotFormat=txt` gives...

@malikin hmm... that's strange. I'll test it again, maybe it was some mistake on my part

@malikin I'm still getting a JSON format. Are you using Windows or a different OS? I'm using Windows, and here are my configurations and the command I'm running: ``` dbchangelogs/master-changelog.xml...

@malikin the configuration does say json... ``` ---------------------------- [INFO] driver: null [INFO] url: jdbc:h2:tcp://localhost:9090/mem:dev [INFO] username: ***** [INFO] password: ***** [INFO] use empty password: false [INFO] properties file: null [INFO]...

Hi @jgarec and @jasonlyle88, thank you for reporting this issue and for the insightful discussion. I could replicate this bug for Oracle, MySQL, MSSQL and PostgreSQL. It doesn't affect the...

@jasonlyle88 thank you for your feedback. Firstly I want to reassure you that the `triaged` label doesn't mean that we are done with this issue - it's just an internal...

Hi @amazing4u, thank you for reporting this issue. I have been able to replicate it and I agree that the error message should contain more information. I'll be forwarding this...