If a user supplies a malformed jdbc URI, the error thrown is opaque. There needs to be some better detection of error conditions. The following should be done:
[x] Wrap the connection setup in a try/catch to provide more verbose errors
[ ] This class should be more Scala-like and should have the connection be an Option type to force handling of nulls
[x] When logging is implemented, the setup and teardown of the connection should be logged
Fixed the original intent of this bug. The Option type on the connection would be easier if it were done after the tests were refactored. Will open another ticket for that.
If a user supplies a malformed jdbc URI, the error thrown is opaque. There needs to be some better detection of error conditions. The following should be done: