Fix inconsistencies in indexes documentation #83
Closed
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.
Description
Fix inconsistencies in indexes documentation. The table creation and insertion used completely different column names. Creation used
customer_id
, while insertion usedplayerid
. Also, there was a typo inuppder_customer_id
(extrad
) and a space too much inupper _customer_id
.I went for
playerid
andupper_playerid
because the other examples on the page use this name as well. Note that the other examples on the page are a bit inconsistent as well, but at least they are not step-by-step instructions like in this example on virtual columns.When should this PR be released to the public?
immediate release
Documentation Checklist
make start-local
(or using this tutorial)If this PR touches a function implementation (aggregate, scalar, or table-valued):
parent
of my docs page is set correctly and the function shows up in the right category of the table of contents