X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5BDD3D1D068 for ; Fri, 23 Apr 2004 16:40:40 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 51615-03 for ; Fri, 23 Apr 2004 16:40:38 -0300 (ADT) Received: from latenight.fiasco.org.il (latenight.fiasco.org.il [192.117.122.39]) by svr1.postgresql.org (Postfix) with SMTP id 08224D1CCA2 for ; Fri, 23 Apr 2004 16:40:36 -0300 (ADT) Received: (qmail 20188 invoked from network); 23 Apr 2004 19:40:35 -0000 X-Scanned-By: AMaViS-ng at latenight.fiasco.org.il Received: from unknown (HELO shemesh.biz) (192.117.102.130) by latenight.fiasco.org.il with SMTP; 23 Apr 2004 19:40:34 -0000 Message-ID: <40897131.6020902@shemesh.biz> Date: Fri, 23 Apr 2004 22:40:33 +0300 From: Shachar Shemesh Organization: Lingnu Open Source Consulting User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5 X-Accept-Language: en, he MIME-Version: 1.0 To: Stephan Szabo Cc: Robert Treat , Dennis Bjorklund , Bruce Momjian , PostgreSQL-development , PostgreSQL advocacy Subject: Re: [HACKERS] What can we learn from MySQL? References: <1082735128.22969.1106.camel@camel> <20040423094236.J17459@megazone.bigpanda.com> In-Reply-To: <20040423094236.J17459@megazone.bigpanda.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/228 X-Sequence-Number: 4200 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/