Re: Case-Insensitve Text Comparison - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Case-Insensitve Text Comparison
Date
Msg-id 95B7698E-DAAE-4D03-9C33-C9FEAA3E966C@kineticode.com
Whole thread Raw
In response to Re: Case-Insensitve Text Comparison  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Responses Re: Case-Insensitve Text Comparison  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
List pgsql-hackers
On Jun 3, 2008, at 12:06, Zdenek Kotala wrote:

> It is simple. SQL standard does not specify notation for that  
> (chapter 11.34). But there is proposed notation:
>
> CREATE COLLATION <collation name> FOR <character set specification>  
> FROM <existing collation name> [ <pad characteristic> ] [ <case  
> sensitive> ] [ <accent sensitive> ] [ LC_COLLATE <lc_collate> ]  
> [ LC_CTYPE <lc_ctype> ]
>
> <pad characteristic> := NO PAD | PAD SPACE
> <case sensitive> := CASE SENSITIVE | CASE INSENSITIVE
> <accent sensitive> := ACCENT SENSITIVE | ACCENT INSENSITIVE
>
>
> You can specify for each collation if it is case sensitive or not  
> and collation function should be responsible to correctly handle  
> this flag.

Wooo! Now if only i could apply that on a per-column basis. Still,  
it'll be great to have this for a whole database.

Thanks, looking forward to it.

David



pgsql-hackers by date:

Previous
From: Zdenek Kotala
Date:
Subject: Re: Case-Insensitve Text Comparison
Next
From: Zdenek Kotala
Date:
Subject: Re: Case-Insensitve Text Comparison