luckyframework / luckyframework/avram
Add support for composite primary keys
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Crystal
- Stars
- 183
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Composite (PRIMARY KEY (id_1, id_2))
Extracted from #96
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
No files, tests, or entry points are identified in the issue. Start by reviewing issue #96 and Avram's existing primary-key and migration behavior, then define the supported composite-key scope and verify that declarations such as PRIMARY KEY (id_1, id_2) work through the relevant database operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100