From 10edcc0430dc0f5f10a08de6b008b6df2403022f Mon Sep 17 00:00:00 2001 From: Johannes Zick Date: Mon, 26 Nov 2018 17:52:47 +0100 Subject: [PATCH] Warn about dropped Quartz tables The default init scripts drop all tables, as in [the Postgres script](https://github.com/quartz-scheduler/quartz/blob/master/quartz-core/src/main/resources/org/quartz/impl/jdbcjobstore/tables_postgres.sql). Since the only options are `always` or `never`, they are useless for most production settings. More importantly, they deserve a warning, as they should not be used carelessly. --- .../src/main/asciidoc/spring-boot-features.adoc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc index ccbe294cd92a..af96c8386be8 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc @@ -6305,9 +6305,10 @@ following example: spring.quartz.jdbc.initialize-schema=always ---- -NOTE: By default, the database is detected and initialized by using the standard scripts -provided with the Quartz library. It is also possible to provide a custom script by -setting the `spring.quartz.jdbc.schema` property. +WARNING: By default, the database is detected and initialized by using the standard scripts +provided with the Quartz library. These scripts drop existing tables, deleting all triggers +on every restart. It is also possible to provide a custom script by setting the +`spring.quartz.jdbc.schema` property. To have Quartz use a `DataSource` other than the application's main `DataSource`, declare a `DataSource` bean, annotating its `@Bean` method with `@QuartzDataSource`. Doing so