anchor.diff:    matched by the query (regardless of whether any data was changed).
   * `boolean`: returns true if the update count is greater than zero.
   
  +[reftext="SqlUpdate-GetGeneratedKeys"]
   ===== @GetGeneratedKeys
   
   Some SQL statements will cause data to be generated on your behalf at the
  
positive.code: 
  ==== @SqlBatch
  
  TODO:
  
  * Analogous to PreparedBatch in core
  * Execute a statement multiple times, using a series of input arguments.
  * Useful for e.g. batch inserts, batch updates on the same table
  * Method parameters that look like collections will be used as successive
    elements in the batch. All collection parameters will be zipped.
  * Method parameters that don't look like collections will be bound to that
    same value for every element in the batch.
  * All parameters are zipped into a series, and then the batch executes the
    statement for each set of arguments in the series.
  * Returns void, int[] or long[] (update counts per batch statement), or
    boolean[] (update count > 0 per batch statement).
  * Use @GetGeneratedKeys to return containers of generated keys
  * Use @SingleValue for arguments that should be treated as single values, that
    Jdbi would otherwise container a collection.
  
  ==== @SqlCall
  
  
negative.code: The `@RegisterConstructorMapper` annotation may be repeated multiple times on
  the same type or method to register multiple constructor mappers.
  
  [reftext="SqlQuery-SingleValue"]
  ===== @SingleValue
  
  Sometimes when using advanced SQL features like Arrays, a container type like
  