Let jOOQ keep open PreparedStatements

We're going to be implementing a series of performance improvements for the issue you've helped discover in jOOQ: https://github.com/jOOQ/jOOQ/issues/3225

To be fair, the jOOQ benchmark could profit from keeping open `PreparedStatement` references between consecutive query executions. It won't make too much of a difference given the bottleneck in https://github.com/jOOQ/jOOQ/issues/3225, but at least it is more comparable to the plain JDBC solution.

We'll keep you posted, and thanks again for helping us discover this issue
Merge pull request #121 from aaberg/release-1.5.x

Prepare release 1.5.x
Merge pull request #122 from lukaseder/patch-2

Let jOOQ keep open PreparedStatements
ref #123
Merge pull request #124 from dimzon/master

fixes #123
better object construction
less "surprises" for POJO inheritance
thread-safety issue
better inheritance hierarchy walk
Merge pull request #127 from dimzon/master

some fixes and object creation inconsistence fix
setter must have exatly 1 parameter
Merge pull request #129 from dimzon/master

setter must have exatly 1 parameter
updated maven release plugin to fix a compatibility issue with newest version of git
[maven-release-plugin] prepare release sql2o-1.5.0-RC1
[maven-release-plugin] prepare for next development iteration
fixes #130, returnGeneratedKeysByDefault should be false for oracle quirks.
fixed #131 - add possibility to close connection when ResultSetIterable is closed
[maven-release-plugin] prepare release sql2o-parent-1.5.0-RC2
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release sql2o-parent-1.5.0
[maven-release-plugin] prepare for next development iteration