better support for postgres array/hstore types
See original GitHub issueCurrently the input for an array is a literal, i.e for a column of type text[]
the input value has to be a string as follows: "{hello,world}"
. We should do the appropriate mapping to json arrays.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:72
- Comments:39 (8 by maintainers)
Top Results From Across the Web
Documentation: 15: F.18. hstore - PostgreSQL
This module implements the hstore data type for storing sets of key/value pairs within a single PostgreSQL value. This can be useful in...
Read more >choosing between arrays, json and hstore datatypes in ...
Although it may not be a common case to store other types than string in a dictionary, it is still worth to have...
Read more >Support for pgsql array, hstore? - Google Groups
Hello group, Any tips for supporting postgresql varchar[] and hstore column types? At the moment I have Sql2o 1.5.1 filling in a POJO...
Read more >An Introduction to PostgreSQL's hstore - IBM
hstore can be used with, rather than a replacement for, the JSON and JSONB data types. You might consider hstore if you have...
Read more >PostgreSQL anti-patterns: Unnecessary json/hstore dynamic ...
PostgreSQL has json support – but you shouldn't use it for the great majority of what you're doing. This goes for hstore too,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Is it possible or planned to have the
_contains
filter type for arrays? Arrays seem to work in general but not for filtering.Most importantly, would like to see
_contains
support on arrays