Correcting getGlobalSchemaName to use the correct schema #728
Conversation
This file contains 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
challgren
commented
Jul 17, 2024
|
@markstory might be already out for CakeFest. I will check this out if he's not available for a long time. |
Thanks! I'll use my branch for now until a solution can be found or this is merged. |
|
I simplified the test as per the advice, I did also update to the latest 4.x branch and will be testing it on production shortly. |
|
Did about 15 deploys on production and demo. No issues with seeding non-public schemas. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When using CakePHP 5.0.9 and Migrations 4.3.1, if you are using Postgres and try to run the seeds on a schema other than
publicthe seed will fail.