anchor.diff:  
   After executing a database query, you need to interpret the results. JDBC
   provides the *ResultSet* class which can do simple mapping to Java primitives
  -and built in classes, but the API is often cumbersome to use. *Jdbi* provides
  +and built in classes, but the API is often cumbersome to use. Jdbi provides
   configurable mapping, including the ability to register custom mappers for rows
   and columns.
   
  
positive.code: ----
  
  This works for all the collection types supported. For the nested value
  row and column mappers already installed in *Jdbi* will be used.
  Therefore, the following would work and can make sense if the column is nullable:
  
  [source,java]
  ----
  
negative.code: Configuration is managed by the
  link:{jdbidocs}/core/config/ConfigRegistry.html[ConfigRegistry]
  class.  Each Jdbi object that represents a distinct database context
  (for example, Jdbi itself, a *Handle* instance, or an attached SqlObject
  class) gets its own configuration registry.  Most contexts implement the
  link:{jdbidocs}/core/config/Configurable.html[Configurable] interface which
  allows modification of its configuration as well as retrieving the current
  