Re: Keep specialized query pairs, or use single more general but more complex one - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: Keep specialized query pairs, or use single more general but more complex one
Date
Msg-id CAKAnmmJeA-oXD-nOuqpi6EoSogmsgPAW-5puwN1scdc-snEC9g@mail.gmail.com
Whole thread Raw
In response to Keep specialized query pairs, or use single more general but more complex one  (Dominique Devienne <ddevienne@gmail.com>)
Responses Re: Keep specialized query pairs, or use single more general but more complex one
List pgsql-general
On Mon, Feb 24, 2025 at 4:46 AM Dominique Devienne <ddevienne@gmail.com> wrote:
But now we have a new requirement, for "fuzzy find". I.e. the client can ask for names
which are not the exact in-DB names, but also aliases of those names.
... 
join unnest($3::text[]) with ordinality as aliases(name, ord) on c.name = aliases.name

I'm not seeing how this is supposed to work, if these aliases are not in the database somewhere. Maybe an example? How does "Alli" get mapped to a c.name of "Allison"?

 
Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Default Value Retention After Dropping Default
Next
From: Dominique Devienne
Date:
Subject: Re: Keep specialized query pairs, or use single more general but more complex one