anchor.diff:  
   The mapper is selected based on the declared result type of your query.
   
  -*jdbi* iterates over the rows in the ResultSet and presents the mapped results
  +Jdbi iterates over the rows in the ResultSet and presents the mapped results
   to you in a container such as a *List*, *Stream*, *Optional*, or *Iterator*.
   
   [source,java,indent=0]
  
positive.code:   (e.q. `List<T>` for `Seq<T>`). Furthermore ``Multimap<K, T>``s are backed by a `Seq<T>`
    as default value container.
  * Columns can be mapped into Vavr's `Option<T>` type.
  * Tuple projections for *Jdbi*! Yey! Vavr offers Tuples up to a maximum arity of 8.
    you can map your query results e.g. to `Tuple3<Integer, String, Long>`.
    If you select more columns than the arity of the projection the columns
    up to that index will be used.
  
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
  