lightninglabs / lightninglabs/taproot-assets
Remove unnamed constraint from assets table
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
The assets table has an unnamed uniqueness constraint that contains the primary key and as such has no meaning, since the constraint will always be met (See the initial issue #691). Removing it is hard, since it is unnamed and would require a drop and recreate of the table.
See: https://github.com/lightninglabs/taproot-assets/pull/965#discussion_r1651200607
This is not blocking, but should be addressed some time in the future.
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 schema or migration that defines the assets table, then read the context in issue #691 and the discussion on pull request #965. Confirm how the unnamed uniqueness constraint is represented and determine a safe drop-and-recreate path; done means the redundant constraint is removed without losing the table's intended data or primary key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100