Driver::connect() should throw only driver-level exceptions #4072
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Currently, most of the
Driver::connect()
throw aDBALException
on failure but some throw aDriverException
exception. The lower level abstraction (drivers) should not be aware of the higher-level abstraction (DBAL). This way, instead of being implemented in one place, the higher-level logic gets inconsistently duplicated in multiple places.Additional changes
Driver::connect()
is documented as@throws DriverException
.Connection::connect()
is documented as@throws DBALException
.Connection::getDatabasePlatformVersion()
will not expectConnection::connect()
to throw anything else than aDBALException
.Testing
The code being changed is covered by existing tests (e.g.
ExceptionTest::testConnectionException()
). It doesn't look reasonable to add the unit tests that would cover the specific thrown exception types. Ideally, this should be tested statically (e.g. PhpStorm supports that but I'm not sure if other tools that can run on CI do).