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

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

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Shachar Shemesh <psql(at)shemesh(dot)biz>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>,Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>,PostgreSQL advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: [HACKERS] What can we learn from MySQL?
Date: 2004-04-23 20:16:15
Message-ID: 20040423130701.K21905@megazone.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-hackerspgsql-www
On Fri, 23 Apr 2004, Shachar Shemesh wrote:

> 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.

If you can do this in a clean fashion without tromping all around the
code, that'd be reasonable, however, istm that you'd need to either
pre-fold both directions from the given identifier string and pass an
extra copy around or pass the original identifier and its quoted status
and fold on use.  I think either of these are likely to be very intrusive
for what essentially amounts to a transitional feature.

In addition, I'm not sure that this would always work in any case, since
some of those usages may be quoted identifiers that were once generated
from a case-folded string (for example, looking up a name in the catalogs
and quoting it).


In response to

Responses

pgsql-www by date

Next:From: Rod TaylorDate: 2004-04-23 20:28:04
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?
Previous:From: Alexey BorzovDate: 2004-04-23 20:05:33
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?

pgsql-hackers by date

Next:From: Rod TaylorDate: 2004-04-23 20:28:04
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?
Previous:From: Josh BerkusDate: 2004-04-23 20:10:27
Subject: pgFoundry delayed -- some setup issues

pgsql-advocacy by date

Next:From: Rod TaylorDate: 2004-04-23 20:28:04
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?
Previous:From: Alexey BorzovDate: 2004-04-23 20:05:33
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?

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