Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DBAL-867: Doctrine\DBAL\Driver\Connection should be marked as an internal interface #2105

Closed
doctrinebot opened this issue Apr 16, 2014 · 8 comments
Assignees

Comments

@doctrinebot
Copy link

Jira issue originally created by user stof:

Currently, the main entry point Doctrine\DBAL\Connection is documented as a wrapper around Doctrine\DBAL\Driver\Connection.
This is very misleading and encourages other library to typehint against Doctrine\DBAL\Driver\Connection rather than Doctrine\DBAL\Connection. See symfony/symfony#10720 for the original discussion.

However, the discussion in #414 (comment) implies that they should actually not be related together (but it cannot be fixed for BC reasons). The phpdoc should at least be changed

@doctrinebot
Copy link
Author

Comment created by @guilhermeblanco:

This issue was fixed some time ago.

Commit reference: 5fdedc4

@doctrinebot
Copy link
Author

Comment created by @deeky666:

[~guilhermeblanco] How is your commit reference related to this issue?

@doctrinebot
Copy link
Author

Comment created by @guilhermeblanco:

[deeky666] The suggestion about Doctrine\DBAL\Connection and Doctrine\DBAL\Driver\Connection started around the misleading support of ping and how to consistently support it across different drivers.
The commit reference I pointed out is [
beberlei]'s resolution to remove misleading phpdoc around ping support (which is also highlighted in the ticket as "phpdoc should at least be changed").
If there's anything else that is missing, I'm probably not seeing. All I've done is followed dbal's discussion. =\

@doctrinebot
Copy link
Author

Comment created by stof:

Your commit does not fix it at all. [~beberlei]'s comment was about the ping method only indeed. But he explained that Doctrine\DBAL\Connection should actually not be a Doctrine\DBAL\Driver\Connection except for legacy reasons, which is why makign it implement Doctrine\DBAL\Driver\PingableConnection was a bad idea even if it has a ping method.

My issue is related to the description of the class itself:

* A wrapper around a Doctrine\DBAL\Driver\Connection that adds features like

It still describes it as a wrapper around the driver connection, making other devs think that the right typehint in other libraries is the internal driver connection. See the discussion in the Symfony PR I linked

@doctrinebot
Copy link
Author

Comment created by @guilhermeblanco:

So... it's reopened. I'll look into this later today.

@doctrinebot
Copy link
Author

Comment created by @Ocramius:

[~guilhermeblanco] can you re-check this?

@morozov
Copy link
Member

morozov commented Oct 30, 2021

Must have been addressed by #4159.

@morozov morozov closed this as completed Oct 30, 2021
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants