Skip site navigation (1) Skip section navigation (2)

Re: Case-Insensitve Text Comparison

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Case-Insensitve Text Comparison
Date: 2008-06-03 19:18:48
Message-ID: 95B7698E-DAAE-4D03-9C33-C9FEAA3E966C@kineticode.com (view raw or flat)
Thread:
Lists: 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


In response to

Responses

pgsql-hackers by date

Next:From: Zdenek KotalaDate: 2008-06-03 19:26:06
Subject: Re: Case-Insensitve Text Comparison
Previous:From: Zdenek KotalaDate: 2008-06-03 19:06:48
Subject: Re: Case-Insensitve Text Comparison

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group