clockworklabs / clockworklabs/SpacetimeDB
Typescript SDK bug for tables without primary keys
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
There appears to be an issue in the typescript SDK specifically with tables that do not have a primary key.
Symptoms:
When an entry in a table without a primary key is inserted or deleted the change may not be reflected in the client cache and onInsert events may not be fired.
This isn't 100% consistent and I suspect it may be related to inserting and deleting rows within the same transaction.
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 in the TypeScript SDK entry points that handle table changes, client-cache updates, and onInsert events; no specific files or tests are named. Reproduce insertion and deletion for a table without a primary key, including operations in one transaction, then confirm cache state and event delivery are consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100