anchor.diff:  by implementing a few simple interfaces.
   
   [NOTE]
  -Core JDBC features are generally well supported by all database vendors.
  +Core JDBC features are generally well-supported by all database vendors.
   However, more advanced usages like array support or geometry types tend to
   quickly become vendor-specific.
   
  
positive.code:   types. For example, Jdbi provides a generalized <<BeanMapper>>, which maps
    columns to bean properties for any bean class.
  * The mapped type has a generic signature, and/or the mapper could be composed
    from other registered mappers. For example, Jdbi provides a
    <<Map.Entry mapping,Map.Entry<K,V> mapper>>, provided a mapper is registered
    for types `K` and `V`.
  * You want to bundle multiple mappers into a single class.
  
negative.code: 
  The link:{jdbidocs}/core/argument/NamedArgumentFinder[NamedArgumentFinder^]
  interface, as its name suggests, finds arguments by name from some source.
  Typically, a single `NamedArgumentFinder` instance will provide arguments for
  several names.
  
  In cases where neither `bindBean()`, `bindFields()`, `bindMethods()`, nor
  `bindMap()` are a good fit, you can implement your own `NamedArgumentFinder` and
  