fix: schema selection at connection time #7198
Open
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
gsalingu
requested review from
fsamin,
richardlt,
sguiheux and
yesnault
as code owners
Signed-off-by: Gregoire Salingue <[email protected]>
gsalingu
force-pushed
the
fix-schema-selection
branch
from
391d10f
to
2a10c3b
Compare
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.
Description
Fix the schema selection issue encountered with postgresql 16
Related issues
CDS database engine does not account for schema parameter #7197
About tests
Ran locally following the official setup routine: https://ovh.github.io/cds/hosting/ready-to-run/from-binaries/#prepare-database
It fixed the then failing step: https://ovh.github.io/cds/hosting/ready-to-run/from-binaries/#prepare-database
@ovh/cds