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: ----
  
  Two jars are produced, the default one, and an executable one using the Boot plugin with
  classifier '`exec`'    .
  
  For Gradle users the steps are similar. Example:
  
  
negative.code: [[howto-use-custom-entity-manager]]
  === Use a custom EntityManagerFactory
  To take full control of the configuration of the `EntityManagerFactory`, you need to add
  a `@Bean` named '`entityManagerFactory`'. Spring Boot auto-configuration switches off its
  entity manager based on the presence of a bean of that type.
  
  
  