yesodweb / yesodweb/persistent
Support for composite types?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 486
- Forks
- 306
- PR merge metrics
- No merged PRs in 30d
Description
This might be persistent-postgresql rather than persistent but it seems like composite types aren't supported at the moment. This thought was prompted by: https://joncfoo.gitlab.io/posts/2016-06-17-composite-types-with-postgresql.html
I think there's a way to do this by making your own and instances so this is mostly me just musing about formal support.
Additional thought: the most straight-forward way to do this would not furnish a composite type that was reified in the database or that would be usable in that fashion.
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 linked composite-types article and comparing its approach with the persistent and persistent-postgresql packages. Investigate how users currently define their own types and instances, then determine what formal support should mean, including whether the type is reified in PostgreSQL. Done is a documented design and agreed implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100