labeled composite (read)
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 379
- Avg merge
- 14m
- Merged PRs (30d)
- 8
Description
We could derive a new kind of "flat" composite that uses labels rather than offsets to map columns to constructor fields. It could not support nesting but might be nice for some uses, for people who don't care about ɑ-equivalence as much as I do. Perhaps use like:
sql"select * from person".queryL[Person]
and
sql"update ... ".update.withGeneratedKeysL[Person]
We could also add a check for these, to ensure that the column names exist.
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 examining the existing composite mapping APIs and the proposed sql interpolation, queryL, and update.withGeneratedKeysL entry points. Define how label-based flat composites map columns to constructor fields, confirm that nesting is unsupported, and add column-name validation; done means these examples work with the documented constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100