luckyframework / luckyframework/avram
HStore support
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 183
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
https://www.postgresql.org/docs/current/hstore.html
In reality, when creating a new database, you're more likely to define a `jsonb` column than hstore. However, if you already have an hstore field defined, we should have a way to pull that data out and map it to `Hash(String, String)`. Since hstore is a flat key/value pair, you'll only ever get `{} of String => String` from it. Maybe we could have a special type for this.
```crystal
table do
# Treated the same as Hash(String, String)
column data : HStore
end
```
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
The issue names no repository files or tests. Start with the PostgreSQL hstore documentation and inspect the repository's existing database type mappings; done means an hstore column can be declared and its flat key/value data maps to Hash(String, String).
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100