[Snapshots] PK snapshot: NOT NULL unique fallback
Open
Nobody has claimed this yet.
enhancement
snapshot
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 82
- Avg merge
- 18h 22m
- Merged PRs (30d)
- 51
Description
What to build
When a table has no primary key, resolve a NOT NULL unique index as the keyset key (extends the PK-resolution helper).
Requirements
- PK-less table with a NOT NULL unique index snapshots correctly
- Nullable/non-unique indexes are not selected
Depends on
- #926 — PK-resolution catalog helper
- #928 — Walking skeleton: keyset snapshot + batch sizing
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
Start by reading the PK-resolution catalog helper from #926 and the keyset snapshot and batch-sizing work in #928. Extend that resolution path for PK-less tables, then verify that a NOT NULL unique index is selected while nullable and non-unique indexes are rejected, using the snapshot behavior described in the requirements as the completion check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 63/100