From 7ca7eefd1bb6cb8d6fbcb9c00b02fa7650528a5f Mon Sep 17 00:00:00 2001 From: Matthias Stock Date: Thu, 31 Jan 2019 23:34:58 +0100 Subject: [PATCH] Schema generation approach notes Fixes gh-11721 --- .../spring-boot-docs/src/main/asciidoc/howto.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc index 5b706b3d319f..5344856fd07d 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc @@ -2187,6 +2187,7 @@ reused to provide similar features to what the auto-configuration does with a si == Database Initialization An SQL database can be initialized in different ways depending on what your stack is. Of course, you can also do it manually, provided the database is a separate process. +It is recommended to follow a single schema generation approach. @@ -2196,7 +2197,8 @@ JPA has features for DDL generation, and these can be set up to run on startup a database. This is controlled through two external properties: * `spring.jpa.generate-ddl` (boolean) switches the feature on and off and is vendor -independent. +independent. An appropriate configuration is passed to the available JPA implementation +(e.g. Hibernate). * `spring.jpa.hibernate.ddl-auto` (enum) is a Hibernate feature that controls the behavior in a more fine-grained way. This feature is described in more detail later in this guide.