Fix: getDoctrineSchemaManager compatibility with Laravel 11 and Doctrine DBAL 3+ #255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses a compatibility issue when using Laravel 11.x with the
orangehill/iseedpackage.In Laravel 11, calling
getDoctrineSchemaManager()on a database connection throws the following error:Even after installing
doctrine/dbal, the method is not exposed unless accessed via a Doctrine connection manually. Additionally,$this->databaseNamecan be null, which causes:…when fetching connection configuration.
✅ Solution
✅ Tested on: