Re: [PATCH] Completed unaccent dictionary with many missing characters

Поиск
Список
Период
Сортировка
От Ian Lawrence Barwick
Тема Re: [PATCH] Completed unaccent dictionary with many missing characters
Дата
Msg-id CAB8KJ=g9H6dD8w+LMisHtbCyo9vxeqmRcpWaNB=yzU5OyqbFLA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] Completed unaccent dictionary with many missing characters  (Przemysław Sztoch <przemyslaw@sztoch.pl>)
Ответы Re: [PATCH] Completed unaccent dictionary with many missing characters  (vignesh C <vignesh21@gmail.com>)
Список pgsql-hackers
2022年7月13日(水) 19:13 Przemysław Sztoch <przemyslaw@sztoch.pl>:
>
> Dear Michael P.,
>
> 3. The matter is not that simple. When I change priorities (ie Latin-ASCII.xml is less important than Unicode
decomposition),
> then "U + 33D7" changes not to pH but to PH.
> In the end, I left it like it was before ...
>
> If you decide what to do with point 3, I will correct it and send new patches.
>
> What is your decision?
> Option 1: We leave x as in Latin-ASCII.xml and we also have full compatibility with previous PostgreSQL versions.
> If they fix Latin-ASCII.xml at Unicode, it will fix itself.
>
> Option 2:  We choose a lower priority for entries in Latin-ASCII.xml
>
> I would choose option 1.
>
> P.S. I will be going on vacation and it would be nice to close this patch soon. TIA.

Hi

This entry was marked as "Needs review" in the CommitFest app but cfbot
reports the patch no longer applies.

We've marked it as "Waiting on Author". As CommitFest 2022-11 is
currently underway, this would be an excellent time update the patch.

Once you think the patchset is ready for review again, you (or any
interested party) can  move the patch entry forward by visiting

    https://commitfest.postgresql.org/40/3631/

and changing the status to "Needs review".


Thanks

Ian Barwick



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Ian Lawrence Barwick
Дата:
Сообщение: Re: Add semi-join pushdown to postgres_fdw
Следующее
От: Ian Lawrence Barwick
Дата:
Сообщение: Re: Data is copied twice when specifying both child and parent table in publication