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

Class 'Doctrine\DBAL\Driver\PDOPgSql\Driver' not found #4757

Closed
masadi opened this issue Aug 25, 2021 · 4 comments
Closed

Class 'Doctrine\DBAL\Driver\PDOPgSql\Driver' not found #4757

masadi opened this issue Aug 25, 2021 · 4 comments

Comments

@masadi
Copy link

masadi commented Aug 25, 2021

Bug Report

Q A
BC Break yes
Version 3.1.1

Summary

image

Current behaviour

How to reproduce

Expected behaviour

@greg0ire
Copy link
Member

greg0ire commented Aug 25, 2021

Seems related to 99c1b21 . What version of the DBAL are you using?

@masadi
Copy link
Author

masadi commented Aug 25, 2021

Seems related to 99c1b21 . What version of the DBAL are you using?

3.1.1

@greg0ire
Copy link
Member

Duplicate of #4439

@greg0ire greg0ire marked this as a duplicate of #4439 Aug 25, 2021
greg0ire added a commit to greg0ire/framework that referenced this issue Aug 25, 2021
doctrine/dbal is an optional dependency of laravel/framework, and v3 of
the DBAL has been released recently, but obviously, Laravel was never
meant to be compatible with that version.
Users still using Laravel 6 and updating their dependencies get confused
and file invalid reports on the DBAL, see for instance
doctrine/dbal#4439
or
doctrine/dbal#4757

Fixes laravel#24271
greg0ire added a commit to greg0ire/framework that referenced this issue Aug 25, 2021
doctrine/dbal is an optional dependency of laravel/framework, and v3 of
the DBAL has been released recently, but obviously, Laravel 6 was never
meant to be compatible with that version.
Users still using Laravel 6 and updating their dependencies get confused
and file invalid reports on the DBAL, see for instance
doctrine/dbal#4439
or
doctrine/dbal#4757

Fixes laravel#24271
greg0ire added a commit to greg0ire/framework that referenced this issue Aug 25, 2021
doctrine/dbal is an optional dependency of laravel/framework, and v3 of
the DBAL has been released recently, but obviously, Laravel 6 was never
meant to be compatible with that version.
Users still using Laravel 6 and updating their dependencies get confused
and file invalid reports on the DBAL, see for instance
doctrine/dbal#4439
or
doctrine/dbal#4757

Fixes laravel#24271
greg0ire added a commit to greg0ire/framework that referenced this issue Aug 25, 2021
doctrine/dbal is an optional dependency of laravel/framework, and v3 of
the DBAL has been released recently, but obviously, Laravel 6 was never
meant to be compatible with that version.
Users still using Laravel 6 and updating their dependencies get confused
and file invalid reports on the DBAL, see for instance
doctrine/dbal#4439
or
doctrine/dbal#4757

Fixes laravel#24271
greg0ire added a commit to greg0ire/framework that referenced this issue Aug 25, 2021
doctrine/dbal is an optional dependency of laravel/framework, and v3 of
the DBAL has been released recently, but obviously, Laravel 6 was never
meant to be compatible with that version.
Users still using Laravel 6 and updating their dependencies get confused
and file invalid reports on the DBAL, see for instance
doctrine/dbal#4439
or
doctrine/dbal#4757

Fixes laravel#24271
taylorotwell pushed a commit to laravel/framework that referenced this issue Aug 26, 2021
doctrine/dbal is an optional dependency of laravel/framework, and v3 of
the DBAL has been released recently, but obviously, Laravel 6 was never
meant to be compatible with that version.
Users still using Laravel 6 and updating their dependencies get confused
and file invalid reports on the DBAL, see for instance
doctrine/dbal#4439
or
doctrine/dbal#4757

Fixes #24271
taylorotwell pushed a commit to illuminate/database that referenced this issue Aug 26, 2021
doctrine/dbal is an optional dependency of laravel/framework, and v3 of
the DBAL has been released recently, but obviously, Laravel 6 was never
meant to be compatible with that version.
Users still using Laravel 6 and updating their dependencies get confused
and file invalid reports on the DBAL, see for instance
doctrine/dbal#4439
or
doctrine/dbal#4757

Fixes laravel#24271
victorvilella pushed a commit to cdsistemas/framework that referenced this issue Oct 12, 2021
doctrine/dbal is an optional dependency of laravel/framework, and v3 of
the DBAL has been released recently, but obviously, Laravel 6 was never
meant to be compatible with that version.
Users still using Laravel 6 and updating their dependencies get confused
and file invalid reports on the DBAL, see for instance
doctrine/dbal#4439
or
doctrine/dbal#4757

Fixes laravel#24271
@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 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants