Add setDatabase to Jenssegers\Mongodb\Connection #2236
Merged
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
Smolevich
approved these changes
Apr 29, 2021
|
@Smolevich should we backport this? Thanks! |
divine
suggested changes
Apr 29, 2021
divine
approved these changes
Apr 29, 2021
Codecov Report
@@ Coverage Diff @@
## master #2236 +/- ##
============================================
- Coverage 86.93% 86.82% -0.12%
- Complexity 663 664 +1
============================================
Files 33 33
Lines 1554 1556 +2
============================================
Hits 1351 1351
- Misses 203 205 +2
Continue to review full report at Codecov.
|
mnphpexpert
added a commit
to mnphpexpert/laravel-mongodb
that referenced
this pull request
Sep 2, 2024
…patch-1 Add setDatabase to Jenssegers\Mongodb\Connection
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.
We have a use case where the database is determined dynamically and is not known in advance.
Previously, we used
DB::purge()which wasn't ideal as this would cause the previous connection to be closed.This change would allow us to change the database on demand.