Solves problem with postgresql databases in Laravel 11 #294
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
finiteinfinity
approved these changes
Sep 12, 2024
|
@C-ArenA @finiteinfinity I am currently actively using PostgreSQL. While investigating a bug the other day, I ran into an undocumented Laravel function: I think it would be worthwhile to adapt the operation to this, i.e. if data is provided there, it is used. What do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 fixes the
schemas()method to stop using Doctrine. It treats "schemas" as "databases" instead of "PostgreSQL Schemas" as stated in a comment in the same file. It's not a big change, but it now works perfectly with PostgreSQL connections and partially addresses issues #286 and #292.