Re: \w doesn't match non-ASCII letters
От | Markus Bertheau |
---|---|
Тема | Re: \w doesn't match non-ASCII letters |
Дата | |
Msg-id | 1087231009.2649.1.camel@teetnang обсуждение исходный текст |
Ответ на | Re: \w doesn't match non-ASCII letters (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: \w doesn't match non-ASCII letters
|
Список | pgsql-bugs |
=D0=92 =D0=9F=D0=BD=D0=B4, 14.06.2004, =D0=B2 17:25, Tom Lane =D0=BF=D0=B8= =D1=88=D0=B5=D1=82: > Peter Eisentraut <peter_e@gmx.net> writes: > > Markus Bertheau wrote: > >> oocms=3D# select '=D1=84' ~ '^\\w$'; > >> ?column? > >> ---------- > >> f > >> (1 =D0=B7=D0=B0=D0=BF=D0=B8=D1=81=D1=8C) >=20 > > What locale are you using for LC_COLLATE? If it's C or POSIX, you need= =20 > > to change it and re-initdb. >=20 > Another likely cause of trouble is that the regexp character > classification stuff is presently based on <ctype.h> functions and thus > cannot work in multibyte encodings. This is in a UTF-8 database, so yes, these are multibyte characters. Is there something planned to support UTF-8 in regexps? --=20 Markus Bertheau <twanger@bluetwanger.de>
В списке pgsql-bugs по дате отправления: