From: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
---|---|
To: | Joe Van Dyk <joe(at)tanga(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: jsonb and comparison operators |
Date: | 2014-09-03 04:55:46 |
Message-ID: | CAEYLb_WQ5mUNGzBfHsZD_e9ssKCOPXo+7NcMiWcX3skn=Wn=_A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 2, 2014 at 9:38 PM, Joe Van Dyk <joe(at)tanga(dot)com> wrote:
> I want to return all rows that have a value of less than 10. I have
> arbitrary keys I want to check (not just 'a').
If you created an expression B-Tree index on 'a' it would work for
'a', but you'd have to use a jsonb literal, not a json/int4 literal.
If you want to be able to query every key at the top nesting level of
an object, such that all rows are returned with jsonbs that have
object values of which in each case one of them is, say, below 10,
then that's something that no existing opclass can support. But, why
should it be supported? That's a very fuzzy criteria to search on.
--
Regards,
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Van Dyk | 2014-09-03 05:06:45 | Re: jsonb and comparison operators |
Previous Message | Joe Van Dyk | 2014-09-03 04:38:49 | jsonb and comparison operators |