Repository navigation
docs(databases): drop the PostgreSQL reconnect claims - #53
Merged
Merged
Conversation
datlechin
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
TableProApp/TablePro#3271 keeps one connection per PostgreSQL database, so changing database no longer reconnects. The site still says it does.
Change
Removes the claim from the PostgreSQL page (Connect paragraph, CockroachDB paragraph, the "switch-database" FAQ) and the
database-switch-reconnectslimit, in English and Vietnamese. Nothing added.Merge with the release that ships #3271; on 0.77.2 the old copy is still true.
Verified
php artisan test --compact: 1346 passed.