Save a reference to the new handle when reconnecting

After a database disconnect, the current version of the code reconnects just fine, but doesn't seem to actually save the reference, so the next call will just find a handle that looks just as inactive as before, and attempt reconnection again.

This is not only wasteful in terms of reconnection attempts, it actually introduces bugs when the software around it depends on the session being stable between two calls.  (which was my case)

The proposed patch fixes that in a way that's good enough for me (TM).  I have no idea how to reliably test for this.
Check for defined vals, not only exists
Merge pull request #45 from e11it/master

Check is defined for order_by, limit,offset opts param. Added offset param for postgresql.
Merge branch 'patch-1' of git://github.com/jmazon/Dancer-Plugin-Database into pr/44/cache_after_reconnect
Test for caching after reconnect (see PR-44)

A test to ensure that, after a reconnect, the newly-connected handle is cached.

This failed before applying @jmazon's changes from PR-44 and passes after, so
I'm confident now.
Update Changes for shared core
Updating Changes for Dancer1
Bump version for Dancer::Plugin::Database
Bump version for shared core to 0.05
Offset item description
Offset item description(fix formate)
Merge pull request #48 from e11it/master

Offset item description(Issue #46)
POD syntax fixes