Clarify ROWS/RANGE restriction applies to ROW_NUMBER - #10383
Clarify ROWS/RANGE restriction applies to ROW_NUMBER#10383Gabriel Donizeti Candido (donican) wants to merge 2 commits into
Conversation
This article (ROW_NUMBER) doesn't mention that the ROWS/RANGE clause of OVER can't be specified for this function, even though the same restriction applies. The RANK article states this explicitly. This change adds that clarification here to avoid ambiguity for readers.
|
Gabriel Donizeti Candido (@donican) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Gabriel Donizeti Candido (@donican) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit ef5f2c3: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Van To (@VanMSFT) Randolph West MSFT (@rwestMSFT) Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
Co-authored-by: Randolph West MSFT <97149825+rwestMSFT@users.noreply.github.com>
|
Learn Build status updates of commit cf77c16: ✅ Validation status: passed
For more details, please refer to the build report. |
4 participants
This article (ROW_NUMBER) doesn't mention that the ROWS/RANGE clause of OVER can't be specified for this function, even though the same restriction applies. The RANK article states this explicitly. This change adds that clarification here to avoid ambiguity for readers.