
> "In a nutshell I want to use postgres as a back end to an access
> database. This means that all collation done by postgres musht be case
> insensitive including like clauses."
> 
> I left the all the spelling mistakes in place :)

Could a national char implementation that is case insensitive be a solution
here ?
Meaning: is it as simple as setting LC_COLLATE to another value and
configuring
--enable-locale ?
How far is Thomas with the nchar nvarchar types ?
I think national char and national char varying are the correct datatypes
for 
such behavior. Although I think the = operator is still case sensitive for
that datatype.
Replacing = or like for the char and varchar or text datatypes is probably
not possible, 
because it is used internally, but for nchar ... it should be.

Andreas

Wed, 3 May 2000 10:58:51 +0200 
Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>
AW: Why Not MySQL?
> How far is Thomas with the nchar nvarchar types ?

No code written, but I've been thinking about it a little. After 7.0
comes out and things settle down I'll get a discussion going unless
someone beats me to it.

                       - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California

Thu, 04 May 2000 05:15:56 +0000
Thomas Lockhart <lockhart@alumni.caltech.edu>
Re: AW: Why Not MySQL?