Cookbook tip about traditional UNIQUE constraints, the RethinkDB way
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
So a user can learn about concatenating those fields that compose a UNIQUE constraint into the table id and leverage ReQL inserts with conflict options.
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
Review the existing cookbook and documentation for traditional UNIQUE constraints, table ids, and ReQL inserts with conflict options. Add a clear tip explaining how to concatenate the constraint fields into the table id and use the insert conflict options, matching the surrounding documentation style.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100