Using modifySql results in different checksum

[s4iko]

Describe the bug

Hi,
I use Liquibase to update my PostgreSQL database.
A ChangeSet contains:

        <modifySql dbms="postgresql">
            <append value=" PARTITION BY LIST (part_key)"/>
        </modifySql>

This results in a different checksum if I execute it from a JVM and a native application.

I logged the Liquibase checksum calculation and the difference seems to be applyToRollback="false" which is present in the JVM version but not is the native one:

JVM:

Computed checksum for append:[
    applyToRollback="false"
    value=" PARTITION BY LIST (part_key)"
] as 166219fc8b85471d0ccc0e2b680e01aa

native:

Computed checksum for append:[
    value=" PARTITION BY LIST (part_key)"
] as 99c71b4dea606026f09842e45adcb96b

I tried to do a workaround by setting the property applyToRollback in the modifySql element but it didn't change anything.

Thanks

Expected behavior

The checksums are the same in the JVM and native version of the application.

Actual behavior

The checksums are not the same in the JVM and native version of the application.

How to Reproduce?

• Add a changeset with a modifySql element.
• Start the JVM application to update the database then stop it
• Start the native application, an error log notify the checksum change

Output of uname -a or ver

Ubuntu 24.04.2 LTS (on WSL)

Output of java -version

openjdk version "21.0.6" 2025-01-21

Mandrel or GraalVM version (if different from Java)

No response

Quarkus version or git rev

3.22.3

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.8.7

Additional information

No response

[quarkus-bot]

/cc @Karm (native-image), @galderz (native-image), @zakkak (native-image)

[geoand]

Can you please attach a sample application we can use to see the problem in action?

[s4iko]

Hi, sure, here you go.
code-with-quarkus-liquibase-native.zip

To reproduce:

# Build the native executable
mvn install -Dnative -Dquarkus.native.container-build=true

# start the app with JVM
mvn quarkus:dev

# get and set the port used to expose the Postgres started with the dev services
docker ps # get the port of postgres container
export DB_PORT=<postgres port>

# run the native executable with options to connect to the same postgres
./target/code-with-quarkus-1.0.0-SNAPSHOT-runner \
  -Dquarkus.datasource.jdbc.url=jdbc:postgresql://localhost:$DB_PORT/quarkus \
  -Dquarkus.datasource.username=quarkus \
  -Dquarkus.datasource.password=quarkus

then you should get an error such as:

...
Caused by: liquibase.exception.CommandExecutionException: liquibase.exception.ValidationFailedException: Validation Failed:
     1 changesets check sum
          db/changeLog.xml::1::quarkus was: 9:11a66c0a11a5b04990fd4356340ee9bd but is now: 9:7bd6b6064602d07b77e3d5fb49ddbae2
...

[geoand]

#48686 takes care of the issue