Explicitly load database driver class when building the connection pool
Explicitly load database driver class when building the connection pool

When executing via leiningen, the order of class loading is slightly different
than when executing via JAR. The canonical way of initializing a JDBC driver is
to call (Class/forName ...) on it, therefore making the JDBC driver management
machinery aware of it. We weren't explicitly doing this, and were lucky that
execution via leiningen worked.

This patch makes the loading of the driver class explicit, thereby Doing The
Right Thing.

Signed-off-by: Deepak Giridharagopal <d11186354d1ef01ca06ae37d7e23e827da13e85f@puppetlabs.com>

rbrw/puppetdb,mullr/puppetdb,wkalt/puppetdb,johnduarte/puppetdb,nfagerlund/puppetdb,shrug/puppetdb,github/puppetlabs-puppetdb,stahnma/puppetdb,highb/puppetdb,kbrezina/puppetdb,grimradical/puppetdb,jantman/puppetdb,waynr/puppetdb,haus/puppetdb,waynr/puppetdb,highb/puppetdb,wkalt/puppetdb,mullr/puppetdb,cprice404/puppetdb,jantman/puppetdb,ajroetker/puppetdb,puppetlabs/puppetdb,kbrezina/puppetdb,melissa/puppetdb,johnduarte/puppetdb,puppetlabs/puppetdb,stahnma/puppetdb,mullr/puppetdb,grimradical/puppetdb,puppetlabs/puppetdb,kbarber/puppetdb,wkalt/puppetdb,rbrw/puppetdb,jantman/puppetdb,kbarber/puppetdb,johnduarte/puppetdb,kbrezina/puppetdb,ajroetker/puppetdb,waynr/puppetdb,grimradical/puppetdb,rbrw/puppetdb,cprice404/puppetdb,senior/puppetdb,wkalt/puppetdb,nfagerlund/puppetdb,github/puppetlabs-puppetdb,haus/puppetdb,mullr/puppetdb,kbarber/puppetdb,highb/puppetdb,mullr/puppetdb,melissa/puppetdb,stahnma/puppetdb,rbrw/puppetdb,cprice404/puppetdb,nfagerlund/puppetdb,rbrw/puppetdb,waynr/puppetdb,kbarber/puppetdb,senior/puppetdb,senior/puppetdb,senior/puppetdb,grimradical/puppetdb,puppetlabs/puppetdb,melissa/puppetdb,shrug/puppetdb,johnduarte/puppetdb,puppetlabs/puppetdb,github/puppetlabs-puppetdb,ajroetker/puppetdb,kbrezina/puppetdb,shrug/puppetdb,shrug/puppetdb,haus/puppetdb,ajroetker/puppetdb,highb/puppetdb