Horton

Re: [HACKERS] What can we learn from MySQL?

Shachar Shemesh <psql@shemesh.biz>

View thread
From: Shachar Shemesh <psql@shemesh.biz>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Robert Treat <xzilla@users.sourceforge.net>, Dennis Bjorklund <db@zigo.dhs.org>, Bruce Momjian <pgman@candle.pha.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>, PostgreSQL advocacy <pgsql-advocacy@postgresql.org>
Date: 2004-04-23T19:40:33Z
Lists: pgsql-hackers 
Stephan Szabo wrote:

>I've tried just changing the parser to unconditionally casefold to upper.
>First thing that happens is that initdb breaks. In addition, you have
>potential issues with comparisons against the catalog's versions of
>standard functions as such if you allow the case folding to be changed
>after the catalogs are setup.
>  
>
That's not the migration path I was thinking of.

What I was thinking of was:
1. Have a setting, probably per-session. Per database works too.
2. Aside from the folder upper and folder lower, have a third option. 
This is "fold upper, if fails, fold lower. If succeeds, issue a 
warning". This should allow programs that rely on the folding (such as 
initdb) to be debugged during the transition period.

          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting
http://www.lingnu.com/