anchor.diff:  ```
   
   === Insert a Blob
  -Similarly for Blobs (*document* column below is of type ```BLOB```):
  +Similarly for Blobs (_document_ column below is of type ```BLOB```):
   ```java
   byte[] bytes = ...
   Flowable<Integer> count = db
  
positive.code: [![codecov](https://codecov.io/gh/davidmoten/rxjava2-jdbc/branch/master/graph/badge.svg)](https://codecov.io/gh/davidmoten/rxjava2-jdbc)
  <!--[![Maven Central](https://maven-badges.herokuapp.com/maven-central/com.github.davidmoten/rxjava2-jdbc/badge.svg?style=flat)](https://maven-badges.herokuapp.com/maven-central/com.github.davidmoten/rxjava2-jdbc)<br/>-->
  
  JDBC is so much simpler with *rxjava2-jdbc*.
  
  Status: *release candidates on Maven Central*
  
  Maven site reports are [here](http://davidmoten.github.io/rxjava2-jdbc/index.html) including [javadoc](http://davidmoten.github.io/rxjava2-jdbc/apidocs/index.html).
  
  
negative.code: 
  Note above that each question mark in the call statement correponds in order with a call to `in()` or `out(...)`. Once all parameters have been defined then the `in(0, 10, 20)` call drives the running of the query with that input. The output `Flowable` is strongly typed according to the `out` parameters specified.
  
  When you start specifying output `ResultSet`s from the call then you lose output parameter strong typing but gain `ResultSet` mapped strong typing as per normal `select` statements in _rxjava2-jdbc_.
  
  Here's an example for one `in` parameter and two output `ResultSet`s with `autoMap`. You can of course use `getAs` instead (or `get`): 
  
  