Re: Ltree pattern matching - Mailing list pgsql-docs

From Tom Lane
Subject Re: Ltree pattern matching
Date
Msg-id 1696142.1636731424@sss.pgh.pa.us
Whole thread Raw
In response to Ltree pattern matching  (PG Doc comments form <noreply@postgresql.org>)
Responses RE: Ltree pattern matching  (Terry Gilbert <Terry.Gilbert@sas.com>)
List pgsql-docs
PG Doc comments form <noreply@postgresql.org> writes:
> In v12 ltree doc (I've not checked other versions)
> "The behavior of % is a bit complicated. It tries to match words rather than
> the entire label. For example foo_bar% matches foo_bar_baz but not
> foo_barbaz. If combined with *, prefix matching applies to each word
> separately, for example foo_bar%* matches foo1_bar2_baz but not
> foo1_br2_baz.

> I believe foo1 is in error (if I understood the operators), it should be
> foo.

A quick test shows that the examples are correct as stated:

contrib_regression=# select 'foo_bar_baz'::ltree ~ 'foo_bar%'::lquery;
 ?column? 
----------
 t
(1 row)

contrib_regression=# select 'foo_barbaz'::ltree ~ 'foo_bar%'::lquery;
 ?column? 
----------
 f
(1 row)

contrib_regression=# select 'foo1_bar2_baz'::ltree ~ 'foo_bar%*'::lquery;
 ?column? 
----------
 t
(1 row)

contrib_regression=# select 'foo1_br2_baz'::ltree ~ 'foo_bar%*'::lquery;
 ?column? 
----------
 f
(1 row)

I'd be the first to admit that this paragraph doesn't seem to measure up
to our usual standards of clarity, but I'm not sure about what would be
better wording.

            regards, tom lane



pgsql-docs by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Example of json_array_elements
Next
From: Terry Gilbert
Date:
Subject: RE: Ltree pattern matching