fix: Postgres port / add document for CockroachDB #1113
Closed
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
* add provider: Microsoft * documentation * support no tenant setup * fix code style * chore: rename Microsoft provider to AzureADB2C * chore: alphabetical order in providers/index
…" (nextauthjs#919) This reverts commit 6e6a24a.
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nextauthjs/next-auth/qlsi0eddt |
jukbot
changed the title
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.
What:
Improve a document, add a guide for CockroachDB who using self-sign cert or any certs.
Why:
I've found that using connection string with sslmode is not working and make the connection manager broken.
So I change the config to TypeORM object format ref from https://typeorm.io/#/connection-options/postgres--cockroachdb-connection-options
Which it work as usual. So I've investigate the cause it was an issue when parsing connection URI with query params reference from
typeorm/typeorm#6544
typeorm/typeorm#6389
And have been fixed in release >= 0.2.26 typeorm/typeorm#6390
EDITED:
This issue has been fixed in #1093
Checklist: