anchor.diff:  value for you based on whether it thinks your database is embedded (default `create-drop`)
   or not (default `none`). An embedded database is detected by looking at the `Connection`
   type: `hsqldb`, `h2` and `derby` are embedded, the rest are not. Be careful when switching
  -from in-memory to a '`real`'     database that you don't make assumptions about the existence of
  +from in-memory to a '`real`' database that you don't make assumptions about the existence of
   the tables and data in the new platform. You either have to set `ddl-auto` explicitly, or
   use one of the other mechanisms to initialize the database.
   
  
positive.code: Use the `SpringBootServletInitializer` base class, which is picked up by Spring's
  Servlet 3.0 support on deployment. Add an extension of that to your project and build a
  war file as normal. For more detail, see the
  http://spring.io/guides/gs/convert-jar-to-war['`Converting a jar Project to a war`'    ] guide
  on the spring.io website and the sample below.
  
  The war file can also be executable if you use the Spring Boot build tools. In that case
  the embedded container classes (to launch Tomcat for instance) have to be added to the
  war in a `lib-provided` directory. The tools will take care of that as long as the
  dependencies are marked as '`provided`'     in Maven or Gradle. Here's a Maven example
  {github-code}/spring-boot-samples/spring-boot-sample-traditional/pom.xml[in the Boot Samples].
  
  
  
negative.code: 
  To disable the failfast you can set `spring.datasource.continueOnError=true`. This can be
  useful once an application has matured and been deployed a few times, since the scripts
  can act as '`poor man's migrations`' -- inserts that fail mean that the data is already
  there, so there would be no need to prevent the application from running, for instance.
  
  If you want to use the `schema.sql` initialization in a JPA app (with
  