Diff Changelog that is generated drops all the tables in the DB

Liquibase Development
1

Good day to the fellow Liquibase members.
I am using liquibase-core version 4.20.0
I am trying to eliminate hibernate’s role in database management in spring boot.
I have set the property spring.jpa.hibernate.ddl-auto to none.
And this is my plugin configuration in my pom.xml:

org.liquibase
liquibase-maven-plugin
4.29.2

C:/Users/Shreerama/Desktop/oams/oams-be/oams-be/src/main/resources/db/changelog/db.changelog-master.yml
C:/Users/Shreerama/Desktop/oams/oams-be/oams-be/src/main/resources/db/changelog/${formatted.timestamp}_changelog.yml
src/main/resources/db/changelog/generated_changelog.yml
org.postgresql.Driver
jdbc:postgresql://localhost:5432/oams-local?useUnicode=true&characterEncoding=UTF-8&serverTimezone=UTC

myUserName
myPassword
hibernate:spring:com.crinsun.services.Oams.entities?dialect=org.hibernate.dialect.PostgreSQLDialect&hibernate.physical_naming_strategy=org.hibernate.boot.model.naming.CamelCaseToUnderscoresNamingStrategy&hibernate.implicit_naming_strategy=org.springframework.boot.orm.jpa.hibernate.SpringImplicitNamingStrategy
true
true



org.liquibase.ext
liquibase-hibernate6
4.27.0


org.springframework.boot
spring-boot-starter-data-jpa
3.2.4


jakarta.validation
jakarta.validation-api
3.0.2



So anytime i change an entity, and run the mvn liquibase:diff command , ideally it should log the changes that have been made to the model but those not yet in the database.
JPA looks at the persisted entities, and also the snapshot of the DB is captured. Liquibase then uses these two to make the comparison and generate the changelog file with the timestamp as the name of the file.
But it is generating the changesets that drop all the foreign constraints and all the tables in the DB, every time I run this command. How do i fix this issue?
If I have missed providing any additional details, kindly point it out so that i can share them as well .
Thank you

2

Hi @shreeramaAdakoli,

Several bugs has been fixed in the latest version (4.30.0). Could you please try with that version and let me know if this issue is still happening?

Thanks,
Daniel.