Document that schema.sql and data.sql will still be run when using Flyway or Liquibase but discourage their use

Expected Behavior:

• The sql file "src/main/resources/data.sql" is run independent from the database during start up
• The sql file "src/test/resources/data.sql" is run independent from the database on test start

Actual Behavior:

• The sql file "src/main/resources/data.sql" is only run with h2 and not postgres during start up
• The sql file "src/test/resources/data.sql" is only run with h2 and not postgres on test start

Failed approaches:

• Use property "spring.datasource.initialization-mode=always"
• Use property "spring.liquibase.drop-first=true"
• Use property "spring.jpa.hibernate.ddl-auto=create-drop"

Initial analyse:

• With postgres there is no "DataSourceSchemaCreatedEvent" so the DataSourceInitializer.initSchema() is never run.

Example-project: https://github.com/hauer-io/liquibase

[snicoll]

That's the wrong expectation I am afraid. When you run a database migration with Liquibase, this is taking control of the schema and the basic schema.sql & data.sql does not run at all.

Said differently, you can't combine, Execute Liquibase Database Migrations on Startup
and Initialize a database.

The name of the latter section has been renamed in 2.3.x but we could certainly improve the documentation to make that more obvious.

Okay. But then the bug is with H2. Since there both is executed.

[snicoll]

I don't know what you mean by "bug is with H2". This project looks wrong to me as you are using two different initialisation system. Either you use liquibase (or flyway) or either you use the schema/data pair.

Example-project: https://github.com/hauer-io/liquibase
Default profile h2 and postgres profile with postgres. So easy to compare that they behave differently.

[snicoll]

Default profile h2 and postgres profile with postgres. So easy to compare that they behave differently.

They behave differently because one is creating the schema via Hibernate and one does not. According to the documentation, embedded databases are created automatically on startup if you're using JPA. That's a sensible default since the database and its content are destroyed at every run.

I've added the following to the configuration on your app:

spring:
  jpa:
    hibernate:
      ddl-auto: none

To make sure that the database is not created by Hibernate and now the two tests fail the same way as the behaviour is the same. This is what I was trying to say with using two competing schema management feature (i.e. schema.sql & data.sql vs. liquibase).

The initialization-mode set to always in the postgres profile is wrong as well since you're using Liquibase.

So in case of embedded database I have to explicit disable hibernate creation to avoid confusion? Thanks for your support. I was confused since I just change the database.