anchor.diff:  *@UseClasspathSqlLocator* is implemented using the <<ClasspathSqlLocator>>, as described above.
   
   [WARNING]
  -<<ClasspathSqlLocator>> loads files unchanged by default. Using the `@UseClasspathSqlLocator` annotation will strip out comments by default! This may lead to unexpected behavior, e.g. SQL Server uses the `#` character to denote temporary tables. This can be controlled with the `stripComments` annotation attribute.
  +<<ClasspathSqlLocator>> loads a file unchanged by default. Using the `@UseClasspathSqlLocator` annotation will strip out comments by default! This may lead to unexpected behavior, e.g. SQL Server uses the `#` character to denote temporary tables. This can be controlled with the `stripComments` annotation attribute.
   
   [source,java]
   ----
  
positive.code: 
  `Jdbi` instances are thread-safe and do not own any database resources.
  
  Typically applications create a single, shared `Jdbi` instance, and set up
  any common configuration there.  See <<Configuration>> for more details.
  
  `Jdbi` itself does not provide connection pooling or other <<High Availability>>
  
negative.code: === JPA
  
  Using the JPA plugin is a great way to trick your boss into letting you try
  Jdbi. "No problem boss, it already supports JPA annotations, easy-peasy!"
  
  This plugin adds mapping support for a small subset of JPA entity annotations:
  
  