Make SQL query consistent with API syntax expression in code examples #5303
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.
Which issue does this PR close?
This is a minor document fix, does not introduce new features or fix bugs.
Rationale for this change
Examples are provides for both SQL query and DataFrame API respectively, and they should be semantically consistent.
The DataFrame API example on this page calls
filtermethods ondf, but the DataFrame API one does not contains relevant part ofWHEREexpression, this could be confusing for newcomers.What changes are included in this PR?
This PR adds
WHEREexpress to SQL query examples to match API syntax expression.Are these changes tested?
Code blocks should covered by doctest.
Are there any user-facing changes?
No.