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

Re: Case-Insensitve Text Comparison

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Case-Insensitve Text Comparison
Date: 2008-06-03 19:26:06
Message-ID: 48459ACE.4060304@sun.com (view raw or flat)
Thread:
Lists: pgsql-hackers
David E. Wheeler napsal(a):
> 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.

The first step is per database, because it is relative easy. Collation 
per-column is very difficult. It requires a lot of changes (parser, planer, 
executor...) in whole source code, because you need to keep collation 
information together with text data.

It is reason why this task is split to severals part.

		Zdenek

In response to

Responses

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2008-06-03 19:45:12
Subject: Re: Case-Insensitve Text Comparison
Previous:From: David E. WheelerDate: 2008-06-03 19:18:48
Subject: Re: Case-Insensitve Text Comparison

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