I found a solution for the problem. But first I try to explain a little
bit better what the poblem was. When I
searched for a text that contained foreign characters (ä,ö,ü,etc.) the
query found no matching records.
for example:
create table mytesttable(myattribute text);
insert into mytesttable values('FRÜHLING');
select * from mytesttable where myattribute~*'frühling';
The query finds no matching records. But it works if the "special
characters" are the same case (i.e. "frühling",
"Frühling","FRüHLING",etc.)
(frühling is the german word for spring :-) btw)
In postgresql versions before 7.x the parameter --enable-locale was
necessary to search for these
characters. Now I found out that in 7.0 the parameter --enable-recode is
necessary. The manual says that
this parameter is for cyrillic recode support only. But the german
character set ISO-8859-1 (I use) is not
cyrillic. So I was a little confused. I'm not sure what the diffrence
between --enable-locale and
--enable-recode is. Anyway, it seems like --enable-recode is necessary to
make a search on attributes that use german character sets.
PS.: I'm afraid that if you don't have a german character set, you can't
really read this message, because the "special characters" are not
translated. The character "ü" should be shown as a small u with 2 points
above.
Tom Lane wrote:
> werner <[EMAIL PROTECTED]> writes:
> > I'm running the 7.0 beta 3. It seems like queries that use german
> > characters like ü,ä,ö or ß don't work with the ~*
> > Operator (case insensetive regex). It only works with case sensetive
> > queries. So the configure option
> > --enable-locale doesn't have any influence.
>
> This isn't enough information. What exactly do you mean by "doesn't
> work"? What query did you issue, what result did you get, what did
> you expect to get? And which locale are you using?
>
> regards, tom lane
