Create a custom exception list and add to tests

[mmoreram]

No description provided.

[seregazhuk]

It looks like currently only Postgres driver exception is not handled by the deferred object.

Here instead of null we can add a handler and reject a deferred with an exception. For all other drivers, they just forward their exceptions up.

I'll try to fix Postgres driver and add a test for exception handling.

[mmoreram]

@seregazhuk a DBAL should always work with custom exceptions, instead of working with specific ones.

That means that if mysql adapter throws an exception for Timeout, we should catch it and make a conversion per each adapter. AT the end, we should be able to work 100% with custom DBAL namespaces in our code, being able to switch between adapters :)

Could we make that list here?
Then we can cover with tests, and start making adaptations + making all tests green.

[mmoreram]

@seregazhuk started here - #3

[seregazhuk]

@mmoreram Aren't you reinventing the wheel here? Doctrine DBAL already has this logic for mapping driver error cases into exceptions. For example, your case with TableNotFound and MySQL can be found here.

I think that we should somehow reuse doctrine logic, instead of rewriting everything from scratch.

[mmoreram]

@seregazhuk LOL.

Good to hear that.
It seems that we will be able to reuse much more code that I expected :D:D:D

[seregazhuk]

Closing because already implemented in Doctrine.

[mmoreram]

Yes!