Deprecate the doctrine-dbal binary

[derrabus]

Q	A
Type	improvement
BC Break	no
Fixed issues	N/A

Summary

As discussed in #5076, the binary is rarely helpful. In most cases, it's prominent exposure through Composer's vendor/bin directory causes mostly confusion.

[morozov]

Oh… for the first two times I read the subject as "Deprecate the Doctrine DBAL library".

Should we deprecate the commands under the Doctrine\DBAL\Tools\Command namespace and the ConsoleRunner as well?

[derrabus]

Oh… for the first two times I read the subject as "Deprecate the Doctrine DBAL library".

That was my plan after the 4.0 release, so that 5.0 is basically an empty package. 😅

I changed the title. 🙂

Should we deprecate the commands under the Doctrine\DBAL\Tools\Command namespace and the ConsoleRunner as well?

As I said already, at least one of the two commands is valuable from my point of view. The ConsoleRunner is just a bit of boilerplate for boostrapping a console application around the commands. With the binary gone, I don't see any reason to remove the console tools. They have low complexity and are not in our way really.

[morozov]

I need to re-read your answer. I thought that by documenting the ways to build a commend, we can remove them from the package and thereby get rid of the dependency on symfony/console.

[morozov]

Answered in #5076 (comment).

[morozov]

It looks like there hasn't been a follow-up patch that would remove the deprecated code from 4.0.x. Would you mind submitting one, @derrabus?

[derrabus]

Right, I totally forgot about this one. #5337