Non-ASCII locales (was:Re: Imperfect solutions)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 31 May 2001 10:07, Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> We still haven't learned how to do it right, actually.  I think the
> history of the LIKE indexing problem is a perfect example of why fixes
> that work for some people but not others don't survive long.  We put out
> several attempts at making it work reliably in non-ASCII locales, but
> none of them have withstood the test of actual usage.

While this subject is fresh, let me ask the obvious questions:
1.)    What locales do we know are problematic?
2.)    What will happen to user queries and data in those locales?
3.)    What has been fixed for this (last I remember there was an index 
corruption issue, and multiple collation problems)?  The 7.1 HISTORY has the 
blanket statement  'Many multi-byte/Unicode/locale fixes (Tatsuo and others)' 
instead of a list of the actual bugs fixed.

Looking through the archives Ifind some details, such as the function 
locale_is_like_safe()  , and I see other details -- but a concise picture of 
what one can expect operating in a non-locale_is_like_safe() (which  
currently includes ONLY the C and POSIX locales) locale would be, IMHO, 
useful information that people wouldn't have to dredge around for -- and 
should probably go into the current locale docs under the Problems heading.
- --
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7FnLa5kGGI8vV9eERAhaaAKDQjz0l+3JWnEv4Gc6HDvKFWjIXnQCdE3V7
XdWmIpkzQ8syjU7KrkzEwcM=
=mZ7Q
-----END PGP SIGNATURE-----