Re: BUG #13440: unaccent does not remove all diacritics
От | Bruce Momjian |
---|---|
Тема | Re: BUG #13440: unaccent does not remove all diacritics |
Дата | |
Msg-id | 20160216144721.GD31273@momjian.us обсуждение исходный текст |
Ответ на | Re: BUG #13440: unaccent does not remove all diacritics (Teodor Sigaev <teodor@sigaev.ru>) |
Ответы |
Re: BUG #13440: unaccent does not remove all diacritics
|
Список | pgsql-bugs |
On Fri, Feb 12, 2016 at 07:44:22PM +0300, Teodor Sigaev wrote: > >>So I changed the script to handle special cases, and I added those I > >>just mentioned (you will find attached the new version of the script > >>and the generated output for convenience). > > > >Here is the patch, attached. > > I'm inclining to commit this patch becouse it suggests more regular > way to update unaccent rules. That is nice. > > But I have some notices: > 1 Is it possible to do not restrict generator script to Python V2? > Python V2, seems, will go away in near future, and it will not be > comfortable to install V2 for a single task. > 2 As it's easy to see, nowhere in sources of pgsql there is no a > UTF-8 encoding, just ASCII. I don't see reason to make an exception > for this script. How would this affect pg_trgm indexes upgraded by pg_upgrade? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Roman grave inscription +
В списке pgsql-bugs по дате отправления: