anchor.diff:  
   In this example, a new `Jdbi` is defined using specific mappers and other customizations. The `Jdbi` object is exposed to Guice using the annotation passed on the module constructor (`GuiceJdbi` in the example). The link:{jdbidocs}/guice/AbstractJdbiDefinitionModule.html[AbstractJdbiDefinitionModule^] supports both annotation instances and classes, similar to Guice itself.
   
  -[WARNING]
  +[NOTE]
   A Jdbi definition module requires that a DataSource object is bound within Guice using the same annotation or annotation class as is passed into the module constructor. *Creating this data source is outside the scope of a Jdbi definition module!*
   
   When implementing the link:{jdbidocs}/guice/AbstractJdbiDefinitionModule.html#jdbiBinder()[configureJdbi()^] method, a number of convenience methods are available as shown above. These methods return Guice LinkedBindingBuilder instances and allow the full range of bindings that guice supports (classes, instances, providers etc).
  
positive.code: selected from a sequence. We need a way to retrieve these generated values back
  from the database.
  
  [WARNING]
  Databases vary in support for generated keys. Some support only one generated
  key column per statement, and some (such as Postgres) can return the entire row.
  You should check your database vendor's documentation before relying on this
  
negative.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]
  