[docs] outdated information on the website/blog
Open
Nobody has claimed this yet.
good_for_contributors
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
Googling for rethinkdb upsert yields this page as the first result: https://www.rethinkdb.com/blog/answers-to-common-questions/#does-rethinkdb-support-upserts
But it seems the upsert option is no longer supported. The page should be updated to reflect the new equivalent way, which is conflict: "update".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked blog page and locate the section addressing whether RethinkDB supports upserts. Update the outdated wording to reflect the conflict: "update" equivalent, then review the rendered page to confirm it no longer presents upsert as supported.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100