Bruce Momjian wrote:
Well, I have no mention of this problem in the TODO list, so I would like to get a good description of why it isn't working.
Looking at the code, I see upper() is defined in oracle_compat.c (you would think it would be more standard), and it calls toupper(), so it probably works on single-bytes encodings, but not multi-byte ones. Is this correct? is there a way to do multi-byte toupper? Perhaps converting to wide characters and calling towupper()?
---------------------------------------------------------------------------
Oleg Bartunov wrote:
On Mon, 11 Aug 2003, Bruce Momjian wrote:
Not sure. I thought it would work.
No, it doesn't works. Several people already complained about bad unicode support. I recall Tatsuo comment some piece of code. I have a little page http://www.sai.msu.su/~megera/postgres/utf8.html about my experience with UTF8 and cyrillic.
---------------------------------------------------------------------------
Eugeny Balakhonov wrote:
Hello, all!
I have a good question for PostgreSQL FAQ.
How to use string functions (like UPPER()/LOWER()) for non-latin strings? Why UPPER() function doesn't work with my UNICODE PostgreSQL database which contains non-latin characters (like cyrillic)? How to make case insensetive search by text field which contains non-latin characters?
Thanks for your answers!
Best regards Eugeny
Regards, Oleg _____________________________________________________________ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
