clockworklabs / clockworklabs/SpacetimeDB
Align with ANSI SQL standards
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Maybe SpacetimeDB already support these and it is just a problem with the SDK but SQL standards can not be reproduced right now including:
- Allow the same column to be nullable and unique at the same time
- Enable unique constraints across multiple columns
- Add foreign key options like on_delete_strategy: RESTRICT, CASCADE, SET NULL
This issue was brought up originally here:
https://discord.com/channels/1037340874172014652/1138585892857057421/1387162411890376794
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
No files, tests, or entry points are named. Start by tracing how the SDK and database handle nullable/unique columns, composite unique constraints, and foreign-key delete strategies, then review the linked Discord discussion to clarify scope. Done means each listed ANSI SQL behavior is supported and verified with tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100