From b10e136a20e1054d68207033d5837f56ab51139f Mon Sep 17 00:00:00 2001 From: Jose Carvajal Date: Fri, 17 Mar 2023 15:03:11 +0100 Subject: [PATCH] Update docs/src/main/asciidoc/databases-dev-services.adoc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Yoann Rodière --- docs/src/main/asciidoc/databases-dev-services.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/databases-dev-services.adoc b/docs/src/main/asciidoc/databases-dev-services.adoc index 3d4c070eec284..0c6424616383f 100644 --- a/docs/src/main/asciidoc/databases-dev-services.adoc +++ b/docs/src/main/asciidoc/databases-dev-services.adoc @@ -105,7 +105,10 @@ When starting Dev Services (for example, in tests or in DEV mode), you will see [IMPORTANT] ==== -When mapping volumes from your local file system to keep the database data, Quarkus might wipe out all the data if you have configured your application to drop and create the schema using `quarkus.hibernate-orm.database.generation = drop-and-create` (using `quarkus.hibernate-orm.database.generation=none` or `quarkus.hibernate-orm.database.generation=validate` is recommended). Also, using Flyway to migrate your schema when starting the application will modify the database data located at your local file system. +When using Dev Services with Hibernate ORM, by default Quarkus will wipe out the database on application startup, which will wipe out the database data on your Docker host's filesystem. +Configure `quarkus.hibernate-orm.database.generation=none` or `quarkus.hibernate-orm.database.generation=validate` to avoid this behavior. + +Also, using Flyway to migrate your schema when starting the application will modify the database data on your Docker hosts's file system. ==== == Database Vendor Specific Configuration