Closed coolamit closed 5 months ago
The problem was some weird behaviour of composer not wanting to downgrade Doctrine DBAL 4 to 3 which had been installed by some deep dependency of Laravel. Its fixed now with release 0.40.0
by also supporting DBAL 4.
The problem was some weird behaviour of composer not wanting to downgrade Doctrine DBAL 4 to 3 which had been installed by some deep dependency of Laravel. Its fixed now with release
0.40.0
by also supporting DBAL 4.
Thanks @tpetry , much appreciated.
I have a Laravel install (using
11.10.x
) where I wanted to use PostgreSQL. I tried installing this package but it ran into the issue where composer couldn't install this package. It seemed like there was a conflict on the version ofcarbonphp/carbon-doctrine-types
in use which gets installed by Laravel.This is the output I got from composer.
I thought I'll try this out on a fresh install. So I created a new Laravel project (which installed
11.13.x
). I ran into same issue. So I installedlaravel-postgresql-enhanced
package using the--with-all-dependencies
flag usingAnd this installed the
laravel-postgresql-enhanced
package after it downgradedcarbonphp/carbon-doctrine-types
from3.2.0
to2.1.0
.Thoughts? Is this just a matter of updating the dependency versions in the package's composer manifest?