DOC: Add example for multi-column joins using merge
#62016
Merged
Conversation
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
|
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
mroeschke
approved these changes
Oct 5, 2025
|
Thanks @thwait |
jzwick
pushed a commit
to jzwick/pandas
that referenced
this pull request
Oct 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.The goal of this change is to add an explicit example for how to perform a multi-column join. While the existing Comparison with SQL documentation does mention that
mergesupports multiple columns, it is easy to miss and likely requires more research from the user to implement.The reason the new examples are placed inside the
INNER JOINsection is to continue on from the previous existing "merge()also offers..." example, and are intended to read as notes about functionality, which can apply to subsequentJOINtypes.