From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Why no jsonb_exists_path()? |
Date: | 2015-06-10 13:19:29 |
Message-ID: | CAPpHfdvzQKOpM+rZR_NaP9Jr5zZV0BK7KUq89+aQBRHc1xxhPQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Josh,
On Tue, Jun 9, 2015 at 9:16 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Dmitry, Alexander:
>
> I'm noticing a feature gap for JSONB operators; we have no way to do this:
>
> jsonb_col ? ARRAY['key1','key2','key3']
>
What documents do you expect to match this operator?
Such syntax can be interpreted in very different semantics. Checking keys
only at top level, any level, sequence starting from top level ... etc.
'{"key1": "value1", "key2": "value2", "key3": "value3"}'
'{"key1":{ "key2": {"key3: "value"}}}'
'{"key1": "value1"}
'[{"key1": "value1"}, {"key2": "value2"}, {"key3": "value3"}]'
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-06-10 13:28:30 | Re: s_lock() seems too aggressive for machines with many sockets |
Previous Message | Jan Wieck | 2015-06-10 13:18:56 | s_lock() seems too aggressive for machines with many sockets |