clockworklabs / clockworklabs/SpacetimeDB
SQL `identity` column must not imply 'UNIQUE`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Our implementation assumes that the identity constraint implies UNIQUE but:
https://en.wikipedia.org/wiki/Identity_column
It is a common misconception that an identity column will enforce uniqueness; however, this is not the case. If you want to enforce uniqueness on the column you must include the appropriate constraint too.
In other words, is just auto_inc
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the Rust implementation and tests that handle SQL identity columns and determine where identity is treated as implying UNIQUE. Update the behavior so identity provides auto-increment semantics without uniqueness, then run the relevant database tests to verify duplicate identity values are allowed unless a separate UNIQUE constraint is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100