Thomas Mauro Vargiu

@neilime This PR would be useful. Can you update the README without to wait the author?

I'm investigating on it. I think could be a problem with concurrency requests from different processes. The only reason that piece of code could fail, it's with a message with...

Ok. Problem is much serious. I think we have truncated message. Probably I'll write a fix soon

I can't find the problem in the code. I'll activate the logger next week. @Shinhan Can you try injecting a logger you too? I would like to know which message...

The deprecation warning seems to come from Symfony's [DebugClassLoader](https://github.com/symfony/symfony/blob/0b8e5066d4377196f2076d459fd2c1f8a96041c8/src/Symfony/Component/ErrorHandler/DebugClassLoader.php). I think the only way is to disable `E_USER_DEPRECATED` errors in production, but it seems not possible to remove them completely.

Yes, in my mind this should be a fisr refactor in order to start writing a new version compatible with dbal v3 in order to make it easier to migrate....

Working on it I was thinking that missed methods on `ConnectionInterface` can be considered a bug, because we always need those method implementations in our classes, implementations provided by the...

`Doctrine\DBAL\Driver\PDO\Connection` doesn't convert every exception from PDO, then yes, we should probably handle every exception. I will take a closer look at it.

Hi @amigian74, It should be resolved with the 1.10 version. Update the library and try it.

Because we released it for dbal 2.11, that was released for php >= 7.3. I just saw that they change it again later. We can try to do the same....