| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Shaheed Haque <shaheedhaque(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Unable to make use of "deep" JSONB index |
| Date: | 2022-06-13 00:04:40 |
| Message-ID: | CAKFQuwbdruA3kZh7Efxwd_jUX_eYXu63PqVuFnKg3ym3tY0iXg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Jun 12, 2022 at 4:52 PM Shaheed Haque <shaheedhaque(at)gmail(dot)com>
wrote:
> ...USING btree ((snapshot -> 'employee' @? '$.* ? (@.pay_graph !=
> 0)'));
> ...WHERE ((snapshot -> 'employee' @? '$."999" ? (@.pay_graph !=
> 0)'))
>
> To my inexpert eye, given the presence of the wildcard, the above look
> like an exact match. What have I missed?
>
>
The system doesn't see a wildcard. Exact match means identical
characters. The fact that you had to write "given the presence of the
wildcard" is why this is not an exact match.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2022-06-13 02:23:12 | Re: Unable to make use of "deep" JSONB index |
| Previous Message | Shaheed Haque | 2022-06-12 23:51:48 | Re: Unable to make use of "deep" JSONB index |